Drought adjustment techniques and apparatuses for irrigation controllers

ABSTRACT

Irrigation controllers, methods, and computer readable media for altering a watering schedule for an irrigation controller in accordance with determined drought conditions are disclosed. A drought category for a watering zone may be determined. An adjusted landscape evapotranspiration rate may be calculated based on the drought category. The watering schedule for the watering zone may be altered in accordance with the adjusted landscape evapotranspiration rate.

RELATED APPLICATIONS

This application claims priority to U.S. Provisional Pat. App. SerialNo. 63/243,066, which was filed on 10 Sep. 2021, and which is entitledDROUGHT ADJUSTMENT TECHNIQUES AND APPARATUSES FOR IRRIGATIONCONTROLLERS. The foregoing application(s) are incorporated herein intheir entirety.

TECHNICAL FIELD

The present invention relates generally to water conservation. Morespecifically, the present invention relates to an irrigation controllerand associated methods.

BACKGROUND

The growing populations in many parts of the world have led toincreasing strain on water supply systems. In many areas, the cost ofwater has increased along with the need to conserve water generally.Accordingly, it would be advantageous to provide improved irrigationcontrollers and associated methods, particularly during droughtconditions.

SUMMARY

Embodiments of the disclosed subject matter are provided below forillustrative purposes and are in no way limiting of the claimed subjectmatter.

In various embodiments, an irrigation controller may adjust a wateringschedule for a watering zone based on determined drought conditions. Theirrigation controller may be configured to control irrigation of awatering zone in accordance with the watering schedule. The irrigationcontroller may also include: a set of one or more processors; a wateringschedule component for formulating a watering schedule for a wateringzone using at least one processor of the set of one or more processorsbased on at least a landscape evapotranspiration rate for the wateringzone; a drought determination component for determining a droughtcategory for the watering zone; a drought adjustment component forcalculating an adjusted landscape evapotranspiration rate for thewatering zone based on the determined drought category using at leastone processor of the set of one or more processors, wherein the wateringschedule component is further configured to adjust the watering schedulefor the watering zone in accordance with the adjusted landscapeevapotranspiration rate using at least one processor of the set of oneor more processors.

In various embodiments, the drought adjustment component may beconfigured to calculate the adjusted landscape evapotranspiration rateby multiplying a drought factor associated with the drought category bythe landscape evapotranspiration rate.

In various embodiments, the adjusted landscape evapotranspiration rateis less than the landscape evapotranspiration rate.

In various embodiments, the drought factor may be less than 1.0.

In various embodiments, the irrigation controller may further comprise asecond drought factor associated with the determined drought categoryfor calculating an adjusted watering duration.

In various embodiments, the drought adjustment component is configuredto determine the drought category based on user input specifying thedrought category.

In various embodiments, the drought adjustment component is configuredto determine the drought category based on drought data and an estimatedgeographic location of the watering zone.

In various embodiments, the irrigation controller may also comprise atleast two of a server, a local device, and a mobile end-user device.

A method for adjusting a watering schedule stored on an irrigationcontroller based on determined drought conditions is disclosed. Theirrigation controller may be configured to control irrigation of awatering zone in accordance with the watering schedule. The method maycomprise: formulating, using at least one processor of a set of one ormore processors, a watering schedule for a watering zone based on atleast a landscape evapotranspiration rate for a watering zone, whereineach processor of the set of one or more processors comprises a portionof an irrigation controller or is in electronic communication with theirrigation controller; determining a drought category for the wateringzone, calculating, using at least one processor of the set of one ormore processors, an adjusted landscape evapotranspiration rate for thewatering zone based on the determined drought category; and adjusting,using at least one processor of the set of one or more processors, thewatering schedule for the watering zone in accordance with the adjustedlandscape evapotranspiration rate.

In various embodiments, the adjusted landscape evapotranspiration ratemay be calculated by multiplying a drought factor associated with thedetermined drought category by the landscape evapotranspiration rate.

In various embodiments, the adjusted landscape evapotranspiration ratemay be less than the landscape evapotranspiration rate.

In various embodiments, the drought factor may be selectable, within aspecified range, by a user.

In various embodiments, the drought category may be determined based onuser input specifying the drought category.

In various embodiments, the method may also include determining thedrought category based on drought data and an estimated geographiclocation of a watering zone.

In various embodiments, the irrigation controller may comprise at leasttwo of a server, a local device, and a mobile end-user device.

In various embodiments, a computer program product for adjusting awatering schedule stored on an irrigation controller based on determineddrought conditions is disclosed. The irrigation controller may befurther configured to control irrigation of a watering zone inaccordance with the watering schedule. The computer program product mayalso include: a non-transitory computer readable medium; and computerprogram code, encoded on the non-transitory computer readable medium,configured to cause at least one processor of a set of one or moreprocessors to perform steps comprising: formulating a watering schedulefor a watering zone based on at least a landscape evapotranspirationrate for the watering zone; determining a drought category for thewatering zone, calculating an adjusted landscape evapotranspiration ratefor the watering zone based on the determined drought category; andadjusting the watering schedule for the watering zone in accordance withthe adjusted landscape evapotranspiration rate.

In various embodiments, calculating the adjusted landscapeevapotranspiration rate comprises multiplying a drought factorassociated with the drought category by the landscape evapotranspirationrate.

In various embodiments, the adjusted landscape evapotranspiration rateis less than the landscape evapotranspiration rate.

In various embodiments, the drought category is determined based ondrought data and an estimated geographic location of the watering zone.

In various embodiments, the computer program product may also includeprogram code configured to obtain a drought category determined based ondrought data and an estimated geographic location of the watering zone.

In various embodiments, the irrigation controller comprises at least twoof a server, a local device, and a mobile end-user device.

BRIEF DESCRIPTION OF THE DRAWINGS

Exemplary embodiments of the invention will become more fully apparentfrom the following description and appended claims, taken in conjunctionwith the accompanying drawings. Understanding that these drawings depictonly exemplary embodiments and are, therefore, not to be consideredlimiting of the invention’s scope, the exemplary embodiments of theinvention will be described with additional specificity and detailthrough use of the accompanying drawings in which:

FIG. 1 illustrates one embodiment of a multi-zone irrigation controller;

FIG. 2 illustrates one embodiment of a hose faucet irrigationcontroller;

FIG. 3 is a schematic block diagram illustrating one embodiment of anirrigation controller;

FIG. 4 is one embodiment of a soil depth diagram;

FIG. 5 is a flowchart illustrating one embodiment of a method forformulating a watering schedule;

FIG. 6 illustrates one embodiment of a property with multiple wateringzones;

FIG. 7 illustrates one embodiment of a catch cup for measuring appliedirrigation water;

FIGS. 8A-8E illustrate an exemplary watering zone with catch cupsarranged to measure applied irrigation water at various points withinone embodiment of a watering zone;

FIG. 9 is one embodiment of a graphical user interface configured toreceive catch cup data;

FIGS. 10A and 10B illustrate a graphical user interface for inputtingmeasurement values for a catch cup shown together with the userinputting one such value;

FIGS. 11A and 11B illustrate one embodiment of a system configured totransmit water usage notifications;

FIG. 12A is a schematic block diagram illustrating one embodiment of anirrigation system including an irrigation controller;

FIG. 12B is a schematic block diagram illustrating a server, which maycomprise at least a portion of an irrigation controller;

FIG. 12C is a schematic block diagram illustrating an end-user device,which may comprise at least a portion of an irrigation controller;

FIGS. 13A-B illustrate a functional block diagram of one embodiment ofan irrigation controller;

FIGS. 14A-B illustrate a functional block diagram of one embodiment of alocal device, which may comprise at least a portion of an irrigationcontroller;

FIGS. 15A-B illustrate a functional block diagram of one embodiment of aserver, which may comprise at least a portion of an irrigationcontroller;

FIGS. 16A-B illustrate a functional block diagram of one embodiment ofan end-user device, which may comprise at least a portion of anirrigation controller;

FIG. 17 is a flowchart illustrating one embodiment of a method forirrigating a property based at least in part on an estimatedreplenishment point level;

FIG. 18 is a flowchart illustrating one embodiment of a method forformulating a watering schedule based on one or more impermissibleperiods of time;

FIG. 19 is a flowchart illustrating one embodiment of a method forupdating an estimated in-soil water level based on historical weatherdata;

FIG. 20 is a flowchart illustrating one embodiment of a method forformulating a watering schedule based on measurement values for one ormore catch cups;

FIG. 21 is a flowchart illustrating one embodiment of a method forformulating a watering schedule in view of a requested start time;

FIG. 22 is a flowchart illustrating one embodiment of a method forformulating a watering schedule based on one or more impermissibleperiods of time;

FIG. 23 is a flowchart illustrating one embodiment of a method forformulating a watering schedule and transmitting notification includinga set of one or more recommended changes;

FIG. 24 illustrates one embodiment of a drought information screencomprising a map illustrating different categories of droughtconditions;

FIG. 25 illustrates one embodiment of a drought settings user interface;

FIG. 26 illustrates one embodiment of a drought notification userinterface;

FIG. 27 illustrates one embodiment of a drought settings user interface,through which drought settings may be specified;

FIG. 28 illustrates one embodiment of an additional view of the droughtsettings user interface of FIG. 27 ;

FIG. 29 illustrates another embodiment of a drought information screen;

FIG. 30 illustrates one embodiment of a zone application user interface,through which specified drought settings may be applied to a selectedzone or all zones;

FIG. 31 illustrates one embodiment of a zone settings user interface,through which settings for a particular zone may be specified, includingdrought settings;

FIGS. 32A-32B comprise a functional block diagram illustrating oneembodiment of an irrigation controller for adjusting a watering schedulebased on drought conditions;

FIG. 33 is a flow diagram illustrating one embodiment of a method foradjusting a watering schedule based on drought conditions;

FIG. 34 is a flow diagram illustrating another embodiment of a methodfor adjusting a watering schedule based on drought conditions;

FIG. 35 is a flow diagram illustrating another embodiment of a methodfor adjusting a watering schedule based on drought conditions;

FIG. 36A is a table illustrating adjustment of watering duration basedon a drought factor;

FIG. 36B is a table illustrating methods for adjusting watering durationand/or watering frequency;

FIG. 37 is a flow diagram illustrating one embodiment of a method foradjusting a watering schedule based on drought conditions;

FIG. 38 is a flow diagram illustrating another embodiment of a methodfor adjusting a watering schedule based on drought conditions; and

FIG. 39 is a flow diagram illustrating an embodiment of a method foradjusting a watering schedule based on a drought factor.

In accordance with common practice, the various features illustrated inthe drawings may not be drawn to scale. Accordingly, the dimensions ofthe various features may be arbitrarily expanded or reduced for clarity.In addition, some of the drawings may be simplified for clarity. Thus,the drawings may not depict all of the components of a given apparatus(e.g., device) or method. Finally, like reference numerals may be usedto denote like features throughout the specification and figures.

DETAILED DESCRIPTION

Various aspects of the present disclosure are described below. It shouldbe apparent that the teachings herein may be embodied in a wide varietyof forms and that any specific structure, function, or both disclosedherein is merely representative. Based on the teachings herein, oneskilled in the art should appreciate that an aspect disclosed herein maybe implemented independently of any other aspects and that two or moreof these aspects may be combined in various ways, even if notspecifically illustrated in the figures. For example, an apparatus maybe implemented, or a method may be practiced, using any number of theaspects set forth herein whether disclosed in connection with a methodor an apparatus. Further, the disclosed apparatuses and methods may bepracticed using structures or functionality known to one of skill in theart at the time this application was filed, although not specificallydisclosed within the application.

The word “exemplary” is used exclusively herein to mean “serving as anexample, instance, or illustration.” Any embodiment described herein as“exemplary” is not necessarily to be construed as preferred oradvantageous over other embodiments. While the various aspects of theembodiments are presented in drawings, the drawings are not necessarilydrawn to scale unless specifically indicated.

As used in this application, the phrases “an embodiment” or “in oneembodiment” or the like do not refer to a single, specific embodiment ofthe disclosed subject matter. Instead, these phrases signify that theidentified portion or portions of the disclosed subject matter may becombined with other aspects of the disclosure without limitation.

For this application, the phrases “connected to,” “coupled to,” and “incommunication with” refer to any form of interaction between two or moreentities, including mechanical, electrical, magnetic, electromagnetic,and thermal interaction and may also include integral formation. Thephrase “attached to” refers to a form of mechanical coupling thatrestricts relative translation or rotation between the attached objects.The phrases “pivotally attached to” and “slidably attached to” refer toforms of mechanical coupling that permit relative rotation or relativetranslation, respectively, while restricting other relative motion.

The phrase “in electronic communication” indicates that two or morereferenced devices or items are capable of transmitting and receiving,to or from each other, data or information of any form encoded,described or captured in any type of electrical or optical signal.

The phrase “attached directly to” refers to a form of attachment bywhich the attached items are either in direct contact, or are onlyseparated by a single fastener, adhesive, or other attachmentmechanisms. The term “abut” refers to items that are in direct physicalcontact with each other, although the items may be attached, secured,fused, or welded together. The term “integrally formed” refers to a bodythat is manufactured integrally (i.e., as a single piece, withoutrequiring the assembly of multiple pieces). Multiple parts may beintegrally formed with each other if they are formed from a singleworkpiece.

As used herein, the term “generally” indicates that a particular item orcomponent is within 5°, 10°, or 15° of a specified orientation or value.As used herein, the term “substantially” indicates that a particularvalue is within 5%, 10% or 15% of a specified value.

In the figures, certain components may appear many times within aparticular drawing. However, only certain instances of the component maybe identified in the figures to avoid unnecessary repetition ofreference numbers and lead lines. According to the context provided inthe description while referring to the figures, reference may be made toa specific one of that particular component or multiple instances, evenif the specifically referenced instance or instances of the componentare not identified by a reference number and lead line in the figures.

FIG. 1 illustrates one embodiment of a multi-zone irrigation controller100. The multi-zone irrigation controller 100 may have various userinput devices including, but not limited to: one or more input buttons102, a programming dial 104, and a display screen 106. In at least oneembodiment, the display screen 106 may be a touch-responsive displayscreen 106 configured to receive user inputs. However, it will also beunderstood that other embodiments are contemplated which may include anon-touch-responsive display screen 106 that is not configured toreceive user inputs. The display screen 106 may be configured to displayany relevant information to the user, as well as general notificationsand recommendations, which will be described in more detail below.

FIG. 2 illustrates one embodiment of a hose faucet irrigation controller200 that may also be used to control water consumption and perform otherfunctions as described herein. The hose faucet irrigation controller 200may have various user input devices including one or more input buttons202 and a programming dial 204. In other embodiments, the hose faucetirrigation controller 200 may also include a display screen (not shown),which may or may not be a touch-responsive display screen configured toreceive user inputs. The display screen may be configured to display anyrelevant information to the user including general notifications andrecommendations.

The multi-zone irrigation controller 100 and the hose faucet irrigationcontroller 200 illustrated in FIGS. 1 and 2 comprise non-limitingexamples and serve only to illustrate the type of local devices that maybe used to perform the functions identified herein.

FIG. 3 is a schematic block diagram illustrating one embodiment of anirrigation controller 300. The irrigation controller 300 may include oneor more local device(s) 300 a, one or more server(s) 300 b, and one ormore end-user device(s) 300 c. The one or more local device(s) 300 a,one or more server(s) 300 b, and/or one or more end-user device(s) 300 cmay be any type of suitable computing device. A local device 300 a maycomprise, for example, a wall-mounted on-site irrigation controller 100,as illustrated in FIG. 1 , or an on-site hose faucet controller 200, asillustrated in FIG. 2 . In this context “on-site” signifies that thelocal device is in close proximity to the controlled sprinkler system.The server 300 b may comprise, for example, a server having a processor,memory, executable instructions stored in the memory, and networkcommunications hardware. The server(s) 300 b may comprise any type ofcomputing device that provides another computing device with or allowsaccess to data or computational resources. In various embodiments, theend-user device(s) 300 c may comprise, for example, a notebook computer,a laptop computer, a tablet, a mobile phone, a smartphone or a desktopcomputer. The functions identified in this application may be performedby one or more of the local device(s) 300 a, the server(s) 300 b and/orthe end-user device(s) 300 c.

Such as the multi-zone irrigation controller 100 illustrated in FIG. 1and the hose faucet irrigation controller 200 illustrated in FIG. 2 .The local device(s) 300 a, one or more server(s) 300 b, and one or moreend-user device(s) 300 c may be in electronic communication with eachother via one or more router(s) 302 and/or one or more computernetwork(s) 304. However, it will be understood that in at least oneembodiment, the local device(s) 300 a may also be configured to operatein a standalone computing environment with minimal or periodiccommunication with the one or more servers 300 b and the one or moreend-user devices 300 c via the one or more router(s) 302 and/or the oneor more computer networks 304. In alternative embodiments, the localdevice(s) 300 a may communicate frequently with the server(s) 300 band/or the end-user device(s) 300 c with the functions disclosed hereinbeing performed by one or more of the one or more local device(s) 300 a,server(s) 300 b and/or end-user device(s) 300 c.

In general, the systems and methods presented herein may be carried outon any type of computing device via a single user, or by multipledifferent users. The computing devices may optionally be connected toeach other and/or to other resources that are not illustrated in FIG. 3and subsequent figures. Such connections may be wired or wireless, andmay be implemented through the use of any known wired or wirelesscommunication standard, including but not limited to: Ethernet, 802.11a,802.11b, 802.11g, and 802.11n, universal serial bus (USB), Bluetooth,cellular, near-field communications (NFC), Bluetooth Smart, ZigBee,Z-Wave, and the like. In FIG. 3 , by way of example, wiredcommunications are shown with solid lines and wireless communicationsare shown with zig-zag lines (i.e., in the shape of a lightning bolt).

Communications between the various elements of FIG. 3 may be routedand/or otherwise facilitated through the use of one or more router(s)302. The one or more router(s) 302 may be of any type known in the artand may be designed for wired and/or wireless communications through anyknown communications standard including, but not limited to, thoselisted above. The one or more router(s) 302 may facilitatecommunications between the one or more local device(s) 300 a, the one ormore server(s) 300 b, the one or more end-user device(s) 300 c, and theone or more computer network(s) 304.

The one or more computer network(s) 304 may include any type of network,including, but not limited to, local area networks and/or wide areanetworks, or a combination of local and wide area networks. The one ormore computer network(s) 304 may be used to store, retrieve, andcommunicate information, such as data, web pages, web-connectedservices, executable code designed to operate over the Internet, and/orperform other functions that facilitate the provision of informationand/or services over the one or more computer network(s) 304.

FIG. 4 illustrates one embodiment of a soil depth diagram 400, which maybe used to visualize, estimate, track, and predict the water content(i.e., an estimated in-soil water level 408) of a particular soil. Thesoil water content is the quantity of water contained in the soil. Thesoil water content may be expressed as a depth, such as in inches, or,alternatively, may be expressed, for example, as a percentage of thevolume or weight. However, it will be understood that any method ofcalculating and tracking the soil water content of a given soil may alsobe used without departing from the spirit and scope of the presentdisclosure.

Continuing with FIG. 4 , the soil depth diagram 400 may include anin-soil water level 408, in-soil water level depth 409, a root zonedepth 410, in-soil water capacity 420 (which may comprise a percentageof root zone depth 410), in-soil water capacity depth 412, availablewater 414, available water depth 415, readily available water 432,readily available water depth 433, condition specific readily availablewater 422, condition specific readily available water depth 423,allowable depletion 424 (which may comprise a percentage of availablewater 414), a replenishment point level 425, a replenishment point depth430, a permanent wilting point 426 (which may comprise a percentage ofroot zone depth 410) and a permanent wilting point depth 428.

The in-soil water level 408 is an indication of the level or quantity ofwater within a particular region of soil. This level 408 may be referredto in the pertinent art as the “moisture balance.” The in-soil waterlevel 408 may be calculated employing in-soil water level depth 409,which may be specified, for example, in inches. When the in-soil waterlevel 408 is estimated, the in-soil water level 408 may be referred toas an estimated in-soil water level 408. When the in-soil water leveldepth 409 is estimated, the in-soil water level depth 409 may bereferred to as an estimated in-soil water level depth 409.

The root zone depth 410 of a soil may be defined as the depth to which agiven plant’s roots readily penetrate the soil, or alternatively, thedepth in which the predominant root activity of a given plant occurs.Thus, the type of plant may determine the root zone depth 410. The rootzone depth 410 may also be referred to as the effective root depth. Forexample, in some applications the effective root depth may be consideredabout 50% of the maximum root zone depth for a given type of plant. Someexamples of root zone depths may include: four to six inches for annualflowers and ground covers, four to eight inches for cool season turf,six to twelve inches for shrubs and warm season turf, and twelve totwenty-four inches for trees. A default value for the root zone in theirrigation application may comprise, for example, six inches.

The in-soil water capacity 420 of a soil 418 may be defined as themaximum amount of in-soil water left within the root zone depth 410after gravity drainage is complete and downward water flow due togravity becomes negligible. The in-soil water capacity 420 may bemeasured using in-soil water capacity depth 412, which may be specified,for example, in inches. The type of soil 418 may determine the in-soilwater capacity 420. For example, sandy soils have larger pores that candrain quickly, such that gravity drainage in these soils may berelatively quick. However, soils that contain clay may have smallerpores that trap water, such that gravity drainage in these soils takesmore time. The in-soil water capacity 420 may also be referred to in theart as field capacity. In addition, the in-soil water capacity depth 412may be referred to in the art as field capacity depth. When the in-soilwater capacity 420 is estimated, the in-soil water capacity 420 may bereferred to as an estimated in-soil water capacity 420. When the in-soilwater capacity depth 412 is estimated, the in-soil water capacity depth412 may be referred to as an estimated in-soil water capacity depth 412.

The available water 414 comprises the maximum amount of water that maybe available to a plant within a soil 418. The available water 414 maybe measured by the available water depth 415, which may be specified,for example, in inches. The available water 414 may be defined as thetotal water that may be stored between the in-soil water capacity 420and the permanent wilting point 426. The available water 414 is theportion of water in a soil 418 that is available for absorption by theplant. When the available water 414 is estimated, the available water414 may be referred to as an estimated available water 414. When theavailable water depth 415 is estimated, the available water depth 415may be referred to as an estimated available water depth 415.

The readily available water 432 is the maximum amount of water that maybe readily available to a plant in a soil 418. The readily availablewater 432 is water that can be removed from the soil with minimal energyand is thus easily accessible by the plant. The readily available water432 may be measured by the readily available water depth 433, which maybe identified, for example, in inches. The readily available water 432may be defined as the water between the replenishment point level 425and the in-soil water capacity 420. The readily available water 432 mayvary according to, among other things, plant and soil type. In variousembodiments, about 50% of the available water 414 may be considered thereadily available water 432, though other percentages may also be chosenbased on various factors. Even though all of the available water 414 maybe accessed by a given plant, the closer the in-soil water level 408gets to the permanent wilting point 426, the greater the stress theplant will experience. Plant stress and yield loss occur once thecondition specific readily available water 422 has been depleted to orbeyond (i.e., at or below) the replenishment point level 425, which maybe referred to as the maximum allowable depletion 424. Thus, a maximumallowable depletion 424 (which may comprise a percentage of availablewater depth 415) may be calculated or formulated based at least on planttype. The term maximum allowable depletion 424 may be referred to in theart, for example, as allowable depletion or allowable moisturedepletion. In various embodiments, once the in-soil water level 408approaches or reaches the replenishment point level 425, the in-soilwater level 408 may be replenished to bring the in-soil water level 408towards the in-soil water capacity 420, thus increasing the water in thesoil 418. When the readily available water 432 is estimated, the readilyavailable water 432 may be referred to as estimated readily availablewater 432. When the readily available water depth 433 is estimated, thereadily available water depth 433 may be referred to as estimatedreadily available water depth 433.

The replenishment point level 425 may be measured using a replenishmentpoint depth 430, which may be specified, for example, in inches. Thereplenishment point depth 430 extends from the lower edge of the rootzone to the replenishment point level 425. As indicated above, as thein-soil water level 408 extends to or below the replenishment pointlevel 425, plant stress and yield loss will occur.

The condition specific readily available water 422 may be considered thewater between the estimated replenishment point level 425 and anestimated in-soil water level 408. The condition specific readilyavailable water 422 may be measured employing the condition specificreadily available water depth 423, which may be specified, for example,in inches. Please note that the condition specific readily availablewater 422 is distinct from readily available water 432. The conditionspecific readily available water 422 is based on the estimated in-soilwater level 408, while the readily available water 432 is based on adifference between the in-soil water capacity 420 and the replenishmentpoint level 425. When the condition specific readily available water 422is estimated, the condition specific readily available water 422 may bereferred to as estimated condition specific readily available water 422.When the condition specific readily available water depth 423 isestimated, the condition specific readily available water depth 423 maybe referred to as estimated condition specific readily available waterdepth 423.

The permanent wilting point 426 may be defined as the level or point atwhich the plant can no longer obtain sufficient water from the soil tosatisfy its water requirements. The permanent wilting point 426 may bemeasured using the permanent wilting point depth 428, which may bespecified, for example, in inches. Once the permanent wilting point 426has been reached, some plants may not fully recover if water is added tothe soil thereafter.

FIG. 5 illustrates a flowchart of one embodiment of a method 500 forformulating a watering schedule. The method 500 may be practiced with,for example, the multi-zone irrigation controller 100 of FIG. 1 , thehose faucet irrigation controller 200 of FIG. 2 , the irrigationcontroller 300 of FIG. 3 , or any other system or device within thescope of the present disclosure. Similarly, the multi-zone irrigationcontroller 100 of FIG. 1 , the hose faucet irrigation controller 200 ofFIG. 2 , and the irrigation controller 300 of FIG. 3 may operate via themethod 500 illustrated in FIG. 5 , or via other methods within the scopeof the present disclosure. The method 500 may be implemented by one ormore processors (not shown) associated with the multi-zone irrigationcontroller 100 of FIG. 1 , the hose faucet irrigation controller 200 ofFIG. 2 , the irrigation controller 300 of FIG. 3 , or any other systemor device within the scope of the present disclosure.

As shown, the method 500 may begin with step 502 in which the user mayselect which watering zones on the property the user desires to manageas “smart-enabled” watering zones (or “smart zones ”), and whichwatering zones the user desires to manage as “custom zones.” Each smartzone may then be managed entirely or partially by the irrigationcontroller, for example, to keep the estimated in-soil water level 408within each smart zone at or above the replenishment point level 425 (orthe maximum allowable depletion 424). In this manner, the plants in eachof the smart zones may be continuously supplied with enough water forsufficient health, while avoiding overwatering and thus conservingwater. Alternatively, each custom zone may be managed based on manualuser inputs for each custom zone selected by the user.

In step 504, forecast evapotranspiration data may be calculated orreceived for each day in the watering schedule. The forecastevapotranspiration data may be received from one or more institutionsthat track and/or forecast weather data. For example, the forecastevapotranspiration data may be received from the National Oceanic andAtmospheric Administration (NOAA), the Environmental Protection Agency(EPA), the International Water Management Institute (IWMI), and thelike. The forecast evapotranspiration data may be received from theseinstitutions from one or more servers or data repositories in anautomated manner. The forecast evapotranspiration data may also becalculated based on current weather conditions, historical weather data,expected future weather conditions, or any combinations thereof.Alternatively, forecast evapotranspiration data may be manually enteredby the user.

In step 506, forecast precipitation data may be received for each day inthe watering schedule. The forecast precipitation data may also bereceived from one or more institutions that track and/or forecastweather data, as previously mentioned. Like the forecastevapotranspiration data, the forecast precipitation data may be receivedin an automated manner from various servers or data repositories. Invarious embodiments, forecast precipitation data may be manually enteredby the user.

In step 508, impermissible watering periods may be identified for eachday in the watering schedule and for each smart zone. Impermissiblewatering period data may be received from one or more institutions thattrack and/or mandate impermissible watering periods, such as waterutility companies, municipal and/or regional water management agenciesand the like. In various embodiments, impermissible watering period datamay be manually entered by the user.

Table 1 below illustrates various symbols along with their associateddescriptions, as well as calculations related to each symbol. Thevarious symbols and their associated calculations may be implemented insoftware code (not shown) in order to carry out one or more steps of themethod 500 via the one or more processors associated with the irrigationcontrollers and systems of the present disclosure. The symbols,descriptions, and calculations identified in Table 1 are only exemplaryand are not limiting of the manner in which the method 500 may beimplemented.

Table 1 is as follows:

TABLE 1 No. SYMBOL DESCRIPTION CALCULATION (1) Wli Initial water level(day) (i.e., in-soil water level 408) starting-wl OR wlf-previous[previous water level] (2) env-mb-change Change in moisture balance(i.e., in-soil water level 408) due to environmental-only conditionsnet-rainfall - ETc [ETc = crop evapotranspiration] (3) wlf-ex-irr Finalwater level ex irrigation (day) (Note: This is the in-soil water level408 if there is no irrigation.) wli + env-mb-change (4) next-watering-wlWater level on the next day able to irrigate if no irrigation occurs onthe current day (Note: This is the in-soil water level 408 at the end ofthe next day if no irrigation takes place.) wlf-ex-irr + (sum ofenv-mb-change_no_water) (5) should-water? Should irrigation occur in thenext few days? (boolean) (Note: This algorithm is applied to each of theupcoming days in a set of days to determine whether watering ispermissible and desired on that day.) can-water [i.e., each day in setof upcoming days] AND (min (wlf-ex-irr, next -watering-wl) <replenishment-point) (6) max-irrigation Maximum amount of irrigation dueto zone and timer restrictions (MAX_ CYCLES [maximum number of starttimes that irrigation controller hardware supports for a particularperiod] * (max-runtime) [the maximum amount of moisture that the soilcan absorb in a single watering episode and is based on infiltrationrate] * (application-rate) [irrigation application rate considering headtype, etc.] * (application efficiency [a percentage of how much waterreaches the root zone]) / 60 (7) net-irrigation The net irrigation toapply on the current day If (should-water?, minimum of (max-irrigation,maximum of (field-capacity -depth [the maximum amount of water that maybe stored in a particular root zone] - wlf-ex-irr, 0)), 0) (8) wlf Finalwater level including irrigation (day) (Note: This is the final in-soilwater level 408 considering irrigation, precipitation andevapotranspiration.) wlf-ex-irr + net-irrigation

Continuing with step 510 of the method 500, in step 510, estimatedin-soil water levels 408 can be calculated for each smart zone on eachday in the watering schedule based on the forecast evapotranspirationdata (which may comprise data related to a landscape evapotranspiration(ET) rate, which is referenced in Table 5), the forecast precipitationdata, and net irrigation for each smart zone. In this manner, it ispossible to estimate and predict the future daily in-soil water levelsfor each smart zone on each day in the watering schedule in order totake corrective action as needed. In various embodiments, the estimatedin-soil water levels 408 may also be calculated utilizing the symbolsand calculations illustrated above in Table 1. For example: (1) aninitial water level at the beginning of the day for a smart zone may befound utilizing the first symbol and calculation listed in Table 1; (2)a predicted change in moisture balance (i.e., estimated in-soil waterlevel 408) due to environmental-only conditions may be found utilizingthe second symbol and calculation in Table 1; (3) a final estimatedin-soil water level 408 at the end of the day (assuming no irrigationtakes place that day) may be found utilizing the third symbol andcalculation in Table 1; (4) an in-soil water level 408 at the end of thenext day (if no irrigation takes place) may be found utilizing thefourth symbol and calculation in Table 1; (5) a determination of whetherirrigation should occur in the next few days may be found utilizing thefifth symbol and calculation in Table 1; (6) a maximum amount ofirrigation water in light of zone and timer restrictions may be foundutilizing the sixth symbol and calculation in Table 1; (7) a netirrigation watering amount on the current day may be found utilizing theseventh symbol and calculation in Table 1; and (8) a final in-soil waterlevel including all pertinent considerations (e.g., irrigation,precipitation, and evapotranspiration) may be found for each smart zoneutilizing the eighth symbol and calculation listed in Table 1. Onceagain, it should be noted that the calculations, descriptions andsymbols included in Table 1 are merely exemplary and do not limit in anyway the manner in which the method 500 may be implemented.

Table 2 below illustrates additional symbols along with their associateddescriptions and calculations, which may also be implemented to carryout one or more steps of the method 500. The symbols, descriptions, andcalculations identified in Table 2 are only exemplary and are notlimiting of the manner in which the method 500 may be implemented.

Table 2 is as follows:

TABLE 2 No. SYMBOL DESCRIPTION CALCULATION (1) zone-gross-rt Grossruntime to apply desired net-irrigation for a zone (net-irrigation * 60)/ (application-rate * efficiency [a percentage of how much water reachesthe root zone]) (2) gross-rt Gross runtime for the program sum ofzone-gross-rt

Continuing with step 512 of the method 500, in step 512, a total desiredwatering time may be calculated for each smart zone for the next day.The total desired watering time calculations may be based on thepredicted in-soil water levels calculated in step 510. For example, thetotal desired watering time may be calculated to completely refill thein-soil water levels calculated in step 510, or to refill the in-soilwater levels calculated in step 510, as much as possible, given anyrelevant limitations. In various embodiments, the total desired wateringtime may be calculated utilizing the symbols and calculationsillustrated above in Table 2. For example: (1) a gross runtime to applya desired net irrigation amount to a smart zone may be found utilizingthe first symbol and calculation listed in Table 2; and (2) a grossruntime for all zones in a program may be found utilizing the secondsymbol and calculation listed in Table 2. Once again it should be notedthat the calculations, descriptions and symbols included in Table 2 aremerely exemplary and do not limit in any way the manner in which themethod 500 may be implemented.

Table 3 below illustrates additional symbols along with their associateddescriptions and calculations which may additionally be implemented tocarry out one or more steps of the method 500. The symbols,descriptions, and calculations identified in Table 3 are only exemplaryand are not limiting of the manner in which the method 500 may beimplemented.

Table 3 is as follows:

TABLE 3 No. SYMBOL DESCRIPTION CALCULATION (1) d0 Irrigation day endingat midnight (2) d1 Day after irrigation day at midnight d0 + 1 (3) d2Two days after irrigation day at midnight d0 + 2 (4) can-water-tomorrow?Whether can irrigate on d1 (boolean) [i.e., is tomorrow an impermissiblewatering period?] (5) suggested-start Customer supplied suggested starttime or default (Note: If the user has input a suggested start time, itwill be used. Otherwise, the default start time will be used.) if(suggested-start, suggested-start, DEFAULT_START) (6) rstart Restrictionstart time (Note: beginning of an impermissible watering period.) (7)rstop Restriction stop time (Note: end of an impermissible wateringperiod.) (8) has-watering-restrictions? True if rstart is set (boolean)(9) has-normal-restrictions? True when the rstart is before the rstop(boolean) (Note: Normal restrictions extend from, for example, 6:00 AMto 10:00 PM each day, i.e., the start of the restriction period iswithin the same day as the end of the restriction period.) rstart <rstop (10) unrestricted-watering-in (Allowable watering interval if norestrictions exist (Note: How long can the system water until a dailyrestriction (i.e., no watering is permitted on Tuesday and Thursday) isencountered. A time restriction is one in which watering is restrictedwithin particular times within a day.) Interval (suggested-start, if(can-water-tomorrow?, d1, d2)) (11) normal-early-in The early intervalbefore restricted times for normal restrictions (Note: This is thelength of the permissible watering interval before time of dayrestrictions apply after Interval (d0, rstart) midnight on a particularday assuming that normal restrictions apply (i.e., the restriction starttime and restriction in time both fall within the same day).) (12)normal-late-in The late interval after restricted times for normalrestrictions (Note: This is the length of the permissible wateringinterval after the restrictions have been lifted when normalrestrictions apply.) Interval (rstop, if (can-water-tomorrow?, d1 +rstart, d1)) (13) normal-default-in The default to use between early andlate normal intervals for normal restrictions (Note: Using normalrestrictions, is the early or late interval closest to the requestedstart time?) Closest (suggested-start, normal-early-in, normal-late-in)(14) normal-adjusted-default-in Normal default interval, with grossruntime adjustments factored into interval start / stop (Note: Identifya watering interval within the selected early or late watering intervalbased on the amount of watering required to achieve a desired in-soilwater level.) if (normal-default-in = normal-early-in,interval(end(normal-early-in) -gross-rt, end(normal- early-in)),normal-late-in) (15) normal-largest-in Largest of the early and latenormal intervals (Note: Select the larger of the early and lateintervals.) if (normal-early-in > normal-late-in, normal-early-in,normal-late-in) (16) normal-suggested-in Normal interval with thesuggested start as the start time (Note: Length of the interval selectedif the suggested start time is used.) interval (suggested-start,end(normal-default-in)) (17) inverted-in Interval where rstart is laterthan rstop (Note: Using an inverted restriction (i.e., the restrictionperiod begins on one day and ends on the following day), calculate thestart and stop time (the interval) of the watering interval excludingthe restriction.) interval (rstop, rstart) (18) inverted-suggested-inInverted interval with suggested-start at the beginning (Note: Calculatethe inverted interval considering the requested start time.) interval(suggested-start, end(inverted-in)) (19) can-use-suggested -start? Trueif the suggested intervals are large enough to water gross-rt minutes(Note: Is true if either the normal or inverted suggested intervalexceeds the desired gross runtime.) (normal-suggested-in ORinverted-suggested-in) >= gross-rt (20) can-use-default-in? True ifnormal-default-in [internal closest to the suggested start time] is atleast gross-rt minutes normal-default-in >= gross-rt (21) watering-inFinal allowable watering interval selection whenhas-watering-restrictions= false, unrestricted -watering-in WHENhas-normal-restrictions? AND can-use-suggested-start?,normal-suggested-in WHEN has-normal-restrictions ANDcan-use-default-in?, normal-adjusted-default-in WHENhas-normal-restrictions?, normal-largest-in WHENcan-use-suggested-start?, inverted-suggested-in ELSE inverted-in

Continuing with step 514 of the method 500, in step 514, wateringinterval times may be calculated based on the total desired wateringtimes calculated in step 512 taking into further consideration anyimpermissible watering periods. For example, once the total desiredwatering times for each smart zone are known, the method 500 may try tofit the total desired watering times within a permissible wateringperiod. If, however, the total desired watering times for each smartzone do not fit into the permissible watering period, then the method500 may compress each watering interval time for each smart zone and/ortruncate one or more watering interval times for individual smart zones,as will be discussed in more detail herein. In various embodiments, thewatering interval times may be calculated utilizing the symbols andcalculations illustrated above in Table 3. For example: (1) anirrigation day ending at midnight may be represented by the first symbolin Table 3; (2) a day after irrigation day (starting at midnight) may befound utilizing the second symbol and calculation listed in Table 3; (3)a second day after the irrigation day (starting at midnight) may befound utilizing the third symbol and calculation listed in Table 3; (4)a determination of whether or not tomorrow is a permissible irrigationday may be represented by the fourth symbol in Table 3; (5) a suggestedstart time may be represented by the fifth symbol and calculation inTable 3; (6) a restriction start time may be represented by the sixthsymbol in Table 3; (7) a restriction stop time may be represented by theseventh symbol in Table 3; (8) a watering restriction boolean variablemay be represented by the eighth symbol in Table 3; (9) another wateringrestriction boolean variable may be represented by the ninth symbol andcalculation listed in Table 3; (10) an allowable watering interval if norestrictions exist may be found utilizing the tenth symbol andcalculation listed in Table 3; (11) an early interval before restrictedtimes for normal restrictions may be found utilizing the eleventh symboland calculation listed in Table 3; (12) a late interval after restrictedtimes for normal restrictions may be found utilizing the twelfth symboland calculation listed in Table 3; (13) a default interval to usebetween early and late normal intervals for normal restrictions may befound utilizing the thirteenth symbol and calculation listed in Table 3;(14) a normal default interval, with gross runtime adjustments factoredinto interval start/stop times may be found utilizing the fourteenthsymbol and calculation listed in Table 3; (15) a largest of the earlyand late normal intervals may be found utilizing the fifteenth symboland calculation listed in Table 3; (16) a normal interval with thesuggested start as the start time may be found utilizing the sixteenthsymbol and calculation listed in Table 3; (17) an inverted interval maybe found utilizing the seventeenth symbol and calculation listed inTable 3; (18) an inverted interval considering the requested start timemay be found utilizing the eighteenth symbol and calculation listed inTable 3; (19) a determination of whether or not the suggested intervalsare large enough to water the desired gross runtime may be foundutilizing the nineteenth symbol and calculation listed in Table 3; (20)a determination of whether or not the normal-default-in (internalclosest to the suggested start time) is at least the desired grossruntime minutes may be found utilizing the twentieth symbol andcalculation listed in Table 3; and (21) a final allowable wateringinterval selection may be found utilizing the twenty-first symbol andcalculation listed in Table 3. Once again it should be noted that thecalculations, descriptions and symbols included in Table 3 are merelyexemplary and do not limit in any way the manner in which the method 500may be implemented.

Table 4 below illustrates additional symbols along with their associateddescriptions and calculations, which may also be implemented to carryout one or more steps of the method 500. The symbols, descriptions, andcalculations identified in Table 4 are only exemplary and are notlimiting of the manner in which the method 500 may be implemented.

Table 4 is as follows:

TABLE 4 No. SYMBOL DESCRIPTION CALCULATION (1) compression Percentage tocompress gross-rt if the interval calculated is less than gross-rtminutes minimum of (1, watering-in / gross-rt) (2) cycles Number ofcycles the program should run (Note: This is the minimum of the maximumnumber of cycles that a particular timer will support and the number ofcycles that are needed applying the particular compression percentageconsidering infiltration rate.) Minimum of (MAX_CYCLES,max(ceiling((compression) * (zone-gross- rt) / (max-runtime)))) (3)cycle-time Gross runtime for each cycle (each cycle includes multiplezones at different times) Sum of ceiling (zone-gross-rt * compression /cycles) (4) num-zones-watering Number of zones watered in this program(input by user or determined by number of the valves connected) (5)soak-time Minutes to soak between cycles (Note: minutes to soak betweencycles may be zero if the cycle is sufficiently long.) if(num-zones-watering = 1 OR cycle-time < MIN_SOAK_MINS [establishedminimum soak time between cycles or could employ user in input],MIN_SOAK_MINS, 0) (6) start-times Times of day to start each cycle(Note: Starting at the beginning time of the interval, identify a starttime considering the cycle time added to the soak time and repeat ifmore water is needed.) for cycles, loop t = start(watering-in), returnt + cycle-time + soak-time (7) run-times How long to run each zone ineach cycle? (Note: How long should each zone run within each cycle?) Foreach zone, min (max-runtime, ceiling (zone-gross-rt * compression /cycles))

Continuing with step 516 of the method 500, in step 516, start times andtotal scheduled watering times may be calculated for each smart zonebased on the considerations and results obtained in step 514. In variousembodiments, the start times and total scheduled watering times may becalculated utilizing the symbols and calculations illustrated above inTable 4. For example: (1) a percentage to compress a gross runtime maybe found utilizing the first symbol and calculation listed in Table 4;(2) a number of cycles the program may run may be found utilizing thesecond symbol and calculation listed in Table 4; (3) a gross runtime foreach cycle may be found utilizing the third symbol and calculationlisted in Table 4; (4) a number of zones watered in a program may befound utilizing the fourth symbol and calculation listed in Table 4; (5)a number of minutes to soak between cycles may be found utilizing thefifth symbol and calculation listed in Table 4; (6) a time of day tostart each cycle may be found utilizing the sixth symbol and calculationlisted in Table 4; and (7) a run-time (or run-times) may be foundutilizing the seventh symbol and calculation listed in Table 4. Onceagain it should be noted that the calculations, descriptions and symbolsincluded in Table 4 are merely exemplary and do not limit in any way themanner in which the method 500 may be implemented.

In step 518, a watering schedule may be formulated based on the starttimes and total scheduled watering times that were calculated for eachsmart zone in step 516.

Any methods disclosed herein comprise one or more steps or actions forperforming the described method. The method steps and/or actions may beinterchanged with one another. In other words, unless a specific orderof steps or actions is required for proper operation of the embodiment,the order and/or use of specific steps and/or actions may be modified orvarious steps may be combined within the scope of the presentdisclosure.

Referring now to FIG. 6 , an exemplary property 600 with multiplewatering zones is illustrated. The exemplary property 600 of FIG. 6includes seven distinct watering zones 610, 612, 614, 618, 620, 624,626, a structure 616, and a driveway 622. However, it will be understoodthat different properties can have any number of watering zones andnon-watering zones.

FIG. 7 illustrates one embodiment of a catch cup 710 designed to captureand measure water 714 in order to facilitate embodiments of the presentdisclosure described herein. A catch cup 710 may be utilized, forexample, to identify the amount of irrigation water applied by asprinkling system to a particular location on a watered property withina particular period of time. The catch cup 710 may include one or moremeasurement markings 712 configured to indicate a level of the water 714that has been captured by the catch cup 710.

FIGS. 8A-8E illustrate how an exemplary watering zone 800 may utilizecatch cups 710 to measure applied irrigation water at various pointswithin the exemplary watering zone 800 in order to calculate adistribution uniformity of the water received from the sprinkler heads820 throughout the exemplary watering zone 800. FIG. 8A is a legend ofsymbols pertaining to FIGS. 8B-8E. FIG. 8B illustrates the exemplarywatering zone 800 with sprinkler heads 820 regularly spaced throughoutthe exemplary watering zone 800 with no water being emitted from thesprinkler heads 820. FIG. 8C illustrates the exemplary watering zone 800with the sprinkler heads 820 emitting water. FIG. 8D illustrates theexemplary watering zone 800 with sprinkler heads 820 and catch cups 710regularly spaced throughout the exemplary watering zone 800 with nowater being emitted from the sprinkler heads 820. FIG. 8E illustratesthe exemplary watering zone 800 with the sprinkler heads 820 emittingwater, such that the catch cups 710 may capture the water from thesprinkler heads 820 and a distribution uniformity of the water may becalculated for the exemplary watering zone 800. A distributionuniformity value for the applied irrigation water may be calculated, forexample, based on the average of the measurement values (i.e., waterlevels) of all catch cups 710 in the exemplary watering zone 800, theaverage of the measurement values of the lowest quartile of catch cups710 in the exemplary watering zone 800, or any other subset of the catchcups 710 in the exemplary watering zone 800.

FIG. 9 illustrates one embodiment of a graphical user interface 910configured to receive and record catch cup data via a suitable end-userdevice 900. The graphical user interface 910 may include a visualrepresentation of one or more catch cups 912, a visual representation ofa water level 914 associated with each of the one or more catch cups912, a numeric value of the water level 916 associated with each of theone or more catch cups 912, an add catch cup icon 918, and a completedicon 920. In this manner, the graphical user interface 910 can helpsimplify the process of calculating one or more distribution uniformityvalues based on the catch cup data.

FIGS. 10A and 10B illustrate how a user may use her or his finger 1022to enter catch cup data in various embodiments of a graphical userinterface 1010. The graphical user interface 1010 may include a visualrepresentation of one or more catch cups 1012, a visual representationof a water level 1014 associated with each of the one or more catch cups1012, a numeric value representing the water level 1016 associated witheach of the one or more catch cups 1012, and a completed icon 1020. Inthis example, the user may use his or her finger 1022 to enter catch cupdata by selecting a water level 1014 on the visual representation of thecatch cup 1012 by touching the water level 1014 or sliding his or herfinger up and down to adjust the water level 1014 measurement. However,it will be understood that in other embodiments, a touch-responsiveinterface may not be used (e.g., the user may enter the catch cup datavia a mouse pointer, a keyboard, or any other known method.).

FIGS. 11A and 11B illustrate one embodiment of a system 1100 configuredto transmit water usage notifications 1130 a and recommendations to theuser. The system 1100 may include one or more end-user device(s) 300 c,one or more server(s) 300 b, and one or more computer network(s) 304.The one or more server(s) 300 b may be configured to electronicallytransmit the notification 1130 a to the one or more end-user device(s)300 c via the one or more computer network(s) 304. The one or moreend-user device(s) 300 c may then be configured to display a visualrepresentation 1132 a of the notification 1130 a to the user. In thismanner, a user with a non-automated, or partially automated, irrigationcontroller device (not shown) can receive useful information andrecommendations that help the user achieve improved water conservationand irrigation efficiency through manually adjusting the user’snon-automated, or partially automated, irrigation controller device. Forexample, the visual representation 1132 a of the notification 1130 a inFIG. 11A alerts the user to expect rain during the next three days andrecommends that the user turns on the rain delay timer. Similarly, thevisual representation 1132 b of the notification 1130 b in FIG. 11Balerts the user to recommended water schedule changes via a zone column1134 and a recommended changes column 1136 identifying recommended waterschedule changes for one or more watering zones.

FIG. 12A is a schematic block diagram illustrating one embodiment of anirrigation system 1210 including a series of irrigation valves 1230 a-c,one or more weather data provider(s) 1252, and an irrigation controller1200. The irrigation controller 1200 may comprise a local device 1200 a,one or more sensor(s) 1238, one or more router(s) 1202, one or morecomputer network(s) 1204, one or more server(s) 1200 b, and one or moreend-user device(s) 1200 c one or more router(s) 1202, the one or morecomputer network(s) 1204, the one or more server(s) 1200 b, and the oneor more end-user device(s) 1200 c may include, for example, similarcomponents and functionality as those shown in the irrigation controller300 of FIG. 3 and, accordingly, will not be described again.

Each of the irrigation valves 1230 a-c may comprise hardware, such as asolenoid valve, that opens and closes a water flow pathway associatedwith each valve 1230 a-c in response to electrical signals generated bythe irrigation controller 1200. Each of the irrigation valves 1230 a-cmay also include an optional meter 1232 a-c. Each meter 1232 a-c maymonitor the amount of water flowing through each of the valves 1230 a-c.Water meter flow data may be related to the amount of water flowingthrough each of the valves 1230 a-c and may be transmitted wirelessly orvia a wired connection to the local device 1200 a. The water meter flowdata may be in the form of an electronic signal that uniquely identifieseach valve 1230 a-c to which the water meter flow data pertains in orderto distinguish the water meter flow data related to each of the valves1230 a-c. The meters 1232 a-c may be positioned in alternative locationsthroughout the system 1210. For example, a single meter 1232 a-c couldpertain to multiple valves 1230 a-c or all of the valves 1230 a-c. Invarious embodiments, one or more of the valves 1230 a-c could comprisethe hose faucet irrigation controller 200 shown in FIG. 2 . Moreover, inat least one embodiment, the local device 1200 a may be, for example,the multi-zone irrigation controller 100 of FIG. 1 .

As shown, the local device 1200 a may include a processor 1234 a that isdesigned to execute instructions. The processor 1234 a may be of any ofa wide variety of types, including microprocessors with x86-basedarchitecture or other architecture known in the art, application-specific integrated circuits (ASICs), field-programmable gate arrays(FPGA’s), and the like. The processor 1234 a may optionally includemultiple processing elements, or “cores.” The processor 1234 a mayinclude a cache that provides temporary storage of data incident to theoperation of the processor 1234 a.

The local device 1200 a may further include memory 1244 a, which may bevolatile memory (such as random-access memory (RAM)) and/or non-volatilememory (such as a solid -state drive or a hard disk drive). The memory1244 a may include one or more memory modules (not shown), executableinstructions 1246 a, data referenced by such executable instructions1246 a, and/or any other data that may beneficially be made readilyaccessible to the processor 1234 a.

The local device 1200 a may further include network communicationshardware 1236 b to facilitate wired and/or wireless communicationsbetween the local device 1200 a and any other device in the system 1210.The network communications hardware 1236 b may include Ethernetadapters, universal serial bus (USB) adapters, and/or any wirelesshardware utilizing the protocols described previously with reference toFIG. 3 such as Wi-Fi adapters, ZigBee adapters, Z-Wave adapters,Bluetooth adapters, cellular adapters, and/or the like.

The local device 1200 a may also include any number of sensors 1240integrated with the local device 1200 a and/or sensors 1238 that may beseparate from, but in communication with the local device 1200 a. Typesof sensors 1238, 1240 may include, but are not limited to: temperaturesensors, precipitation sensors, soil moisture sensors, humidity sensors,wind sensors, and the like. Examples of local devices 1200 a areprovided in FIGS. 1 and 2 herein.

The local device 1200 a may also include valve communications hardware1248 configured to communicate with and/or control each of the valves1230 a-c associated with the system 1210. The valve communicationshardware 1248 may include, for example, a TRIAC, wiring and/orconnection mechanisms to attach wiring to the local device 1200 a. Inone or more embodiments, the local device 1200 a may communicatewirelessly with one or more of the valves 1230 a-c. Accordingly, thevalve communications hardware 1248 may comprise a wireless transmitterand/or wireless transit for communicating with one or more of the valves1230 a-c. In alternative embodiments, valve communication hardware 1248may also be included in a server or end-user device. A valvecommunications hardware 1248 may be in electronic communication with theprocessor 1234 a. The valve communications hardware 1248 may beconfigured to generate electrical signals to control one or moreirrigation valves 1230 a-c, each of the one or more irrigation valves1230 a-c being associable with at least one watering zone of a property.

The local device 1200 a may additionally include one or more user inputs1242 a configured to receive input from the user. The user inputs 1242 amay be integrated into the local device 1200 a, or may be separate fromthe local device 1200 a and connected to it via a wired or wirelessconnection. The user inputs 1242 a may include elements such astouch-responsive screens, buttons, keyboards, mice, track balls, trackpads, styli, digitizers, digital cameras, microphones, and/or other userinput devices known in the art.

The local device 1200 a may also include one or more user outputs 1250 aconfigured to provide output to the user. The user outputs 1250 a may beintegrated into the local device 1200 a or may be separate from thelocal device 1200 a and connected to it via a wired or wirelessconnection. The user outputs 1250 a may include elements such as adisplay screen, speaker, vibration device, LED or other lights, and/orother output devices known in the art. In some embodiments, one or moreof the user inputs 1242 a may be combined with one or more of the useroutputs 1250 a, as may be the case with a touch-responsive screen.

The local device 1200 a may include various other components not shownor described herein. Those of skill in the art will recognize, with theaid of the present disclosure, that any such components may be used tocarry out embodiments of the present disclosure, in addition to or inthe alternative to the components shown and described in connection withFIG. 1210 .

FIG. 12B is a schematic block diagram illustrating a server 1200 b,which may cooperate with the end-user device 1200 c of FIG. 12C toenable practice of embodiments of the present disclosure withclient/server architecture. In this embodiment, the end-user device 1200c may be configured to function as a “dumb terminal,” that is, it may bemade to function in conjunction with the server 1200 b. For example, invarious embodiments the end-user device 1200 c may be a smartphoneconfigured to merely interface the user with the server 1200 b. However,it will be understood that in other embodiments, the end-user device1200 c may be configured to carry out embodiments of the presentdisclosure in a standalone computing environment (i.e., without relyingon communication with or through other devices). As noted above, theend-user device 1200 c may comprise, for example, a notebook computer, alaptop computer, a tablet, a mobile phone, a smartphone or a desktopcomputer.

Computing functions may be carried out, in various embodiments, by theserver 1200 b and/or by the end-user device 1200 c in variouscombinations. Thus, the processors 1234 b, 1234 c, the memory 1244 b,1244 c, the executable instructions 1246 b, 1246 c, the networkcommunications hardware 1236 b, 1236 c the user inputs 1242 b, 1242 c,and the user outputs 1250 b, 1250 c may be housed in the server 1200 band/or the end-user device 1200 c and may have similar functions tothose components previously described in FIG. 12A.

FIGS. 13A-B illustrate a functional block diagram of one embodiment ofan irrigation controller 1300 configured to control water consumptionand perform other functions. The irrigation controller 1300 may includedata 1302 including, but not limited to: catch cup data 1304, historicalevapotranspiration data 1306, historical weather data 1308,impermissible/permissible watering time data 1310, lowest quartile ofthe catch cup values 1312, catch cup measurement values 1314, forecastevapotranspiration data 1316, forecast weather data 1320, forecastprecipitation data 1322, start time data 1324, water scheduling data1326 and/or weather data 1328. The irrigation controller 1300 may alsoinclude various components configured to receive, process, calculate,store or otherwise utilize the foregoing data 1302 including, but notlimited to: an adjustment of in-soil water level component 1330, anaverage component 1332, a catch cup component 1334, an estimatedirrigation rate component 1336, a forecast evapotranspiration component1338, a future permissible watering time periods component 1340, aforecast precipitation component 1342, a forecast weather component1344, a historical weather component 1346, an impermissible periodidentification component 1348, a nearest identification component 1350,a time computation component 1352, an in-soil water capacity component1360, an in-soil water level component 1362, a lowest quartile averagecomponent 1364, a lowest quartile component 1366, a networkcommunications component 1368, an operating component 1370, areplenishment point component 1371, a replenishment point time component1372, a requested start time component 1374, a start watering timeadjustment component 1376, a total desired watering time component 1380,a total scheduled watering time component 1382, a total permissiblewatering time component 1384, a valve communications component 1386, awater level difference component 1388, a watering schedule component1390, a watering time compression component 1392, a current settingscomponent 1394, a recommended changes component 1396, and a notificationcomponent 1398. The irrigation controller 1300 may use the hardwarecomponents in the local device 1200 a, server 1200 b and/or an end-userdevice 1200 c in FIGS. 12A-C to perform the functions associated witheach of the components identified above. Each of the data and componentsassociated with the irrigation controller 1300 of FIGS. 13A-B will beexplained in more detail below.

FIGS. 14A-B illustrate a functional block diagram of a local device 1400a configured to control water consumption and perform other functions.The local device 1400 a may include various types of data 1302including, but not limited to, catch cup data 1304, historicalevapotranspiration data 1306, historical weather data 1308,impermissible/permissible watering time data 1310, lowest quartile ofthe catch cup values 1312, catch cup measurement values 1314, forecastevapotranspiration data 1316, forecast weather data 1320, forecastprecipitation data 1322, start time data 1324, water scheduling data1326, and/or weather data 1328. The local device 1400 a may also includevarious components configured to receive, process, calculate, store orotherwise utilize the foregoing data 1302 including, but not limited to:an adjustment of in-soil water level component 1330, an averagecomponent 1332, a catch cup component 1334, an estimated irrigation ratecomponent 1336, a forecast evapotranspiration component 1338, a futurepermissible watering time periods component 1340, a forecastprecipitation component 1342, a forecast weather component 1344, ahistorical weather component 1346, an impermissible periodidentification component 1348, a nearest identification component 1350,a time computation component 1352, an in-soil water capacity component1360, an in-soil water level component 1362, a lowest quartile averagecomponent 1364, a lowest quartile component 1366, a networkcommunications component 1368, an operating component 1370, areplenishment point component 1371, a replenishment point time component1372, a requested start time component 1374, a start watering timeadjustment component 1376, a total desired watering time component 1380,a total scheduled watering time component 1382, a total permissiblewatering time component 1384, a valve communications component 1386, awater level difference component 1388, a watering schedule component1390, a watering time compression component 1392, a current settingscomponent 1394, a recommended changes component 1396, and a notificationcomponent 1398. The local device 1400 a may use one or more of thehardware components in the local device 1200 a in FIG. 12A to performthe functions associated with each of the functional componentsidentified above. The data and components associated with the localdevice 1400 a of FIGS. 14A-B will be explained in more detail below.

FIGS. 15A-B illustrate a functional block diagram of a server 1500 bconfigured to control water consumption and perform other functions. Theserver 1500 b may include various types of data 1302 including, but notlimited to, catch cup data 1304, historical evapotranspiration data1306, historical weather data 1308, impermissible/permissible wateringtime data 1310, lowest quartile of the catch cup values 1312, catch cupmeasurement values 1314, forecast evapotranspiration data 1316, forecastweather data 1320, forecast precipitation data 1322, start time data1324, water scheduling data 1326, and/or weather data 1328. The server1500 b may also include various components configured to receive,process, calculate, store or otherwise utilize the foregoing data 1302including, but not limited to: an adjustment of in-soil water levelcomponent 1330, an average component 1332, a catch cup component 1334,an estimated irrigation rate component 1336, a forecastevapotranspiration component 1338, a future permissible watering timeperiods component 1340, a forecast precipitation component 1342, aforecast weather component 1344, a historical weather component 1346, animpermissible period identification component 1348, a nearestidentification component 1350, a time computation component 1352, anin-soil water capacity component 1360, an in-soil water level component1362, a lowest quartile average component 1364, a lowest quartilecomponent 1366, a network communications component 1368, an operatingcomponent 1370, a replenishment point component 1371, a replenishmentpoint time component 1372, a requested start time component 1374, astart watering time adjustment component 1376, a total desired wateringtime component 1380, a total scheduled watering time component 1382, atotal permissible watering time component 1384, a valve communicationscomponent 1386, a water level difference component 1388, a wateringschedule component 1390, a watering time compression component 1392, acurrent settings component 1394, a recommended changes component 1396,and a notification component 1398. The server 1500 b may use one or moreof the hardware components in server 1200 b in FIG. 12B to perform thefunctions associated with each of the functional components identifiedabove. Each of the above data and components associated with the server1500 b of FIGS. 15A-B will be explained in more detail below.

FIGS. 16A-B illustrate a functional block diagram of an end-user device1600 c configured to control water consumption and perform otherfunctions. The end-user device 1600 c may include data 1302 including,but not limited to: catch cup data 1304, historical evapotranspirationdata 1306, historical weather data 1308, impermissible/permissiblewatering time data 1310, lowest quartile of the catch cup values 1312,catch cup measurement values 1314, forecast evapotranspiration data1316, forecast weather data 1320, forecast precipitation data 1322,start time data 1324, water scheduling data 1326, and/or weather data1328. The end-user device 1600 c may also include various componentsconfigured to receive, process, calculate, store or otherwise utilizethe foregoing data 1302 including, but not limited to: an adjustment ofin-soil water level component 1330, an average component 1332, a catchcup component 1334, an estimated irrigation rate component 1336, aforecast evapotranspiration component 1338, a future permissiblewatering time periods component 1340, a forecast precipitation component1342, a forecast weather component 1344, a historical weather component1346, an impermissible period identification component 1348, a nearestidentification component 1350, a time computation component 1352, anin-soil water capacity component 1360, an in-soil water level component1362, a lowest quartile average component 1364, a lowest quartilecomponent 1366, a network communications component 1368, an operatingcomponent 1370, a replenishment point component 1371, a replenishmentpoint time component 1372, a requested start time component 1374, astart watering time adjustment component 1376, a total desired wateringtime component 1380, a total scheduled watering time component 1382, atotal permissible watering time component 1384, a valve communicationscomponent 1386, a water level difference component 1388, a wateringschedule component 1390, a watering time compression component 1392, acurrent settings component 1394, a recommended changes component 1396,and a notification component 1398. Each of the above data and componentsassociated with the end-user device 1600 c of FIGS. 16A-B will beexplained in more detail below.

Referring now to FIGS. 13A-B, 14A-B, 15A-B and 16A-B, more specificdescriptions of the data and functional components will be provided. Thecatch cup data 1304 may comprise values representing a water level ineach catch cup 710. The catch cup data 1304 could also include, forexample, an average of the values for all of the cups 710 and/or anaverage of the lowest quartile of the values 1312 of the catch cups 710.

The historical evapotranspiration data 1306 comprises actual dataobserved in the past related to evapotranspiration. This data 1306 maybe obtained from various sources, such as sensor(s) 1238, 1240. Thehistorical evapotranspiration data 1306 may be received from a remoteserver sponsored by one or more weather data provider(s) 1252 and mayinvolve further computation or no computation in order to obtain thehistorical evapotranspiration data 1306.

The historical weather data 1308 comprises actual data observed in thepast related to weather. This data 1308 may be directly obtained usingsensors 1238, 1240 or may be obtained from a remote server utilized byweather data provider(s) 1252. The data 1308 could comprise informationrelated to temperature, precipitation, wind speed and direction,barometric pressure, humidity, etc.

The impermissible/permissible watering time data 1310 may comprise dataindicating when watering is permitted. In various embodiments, legallyimpermissible watering times are considered as well as times whenwatering is unwise, such as watering in the heat of the day.Alternatively, only legally impermissible watering times are considered,such as when watering is prohibited by a municipality or by ahomeowners’ association. In various embodiments, both impermissible andpermissible watering time data 1310 may be obtained via a user input orfrom a remote server. Alternatively, impermissible watering times may beobtained from a remote source, and then the permissible watering timesmay be calculated therefrom. In one or more embodiments, the permissiblewatering times may be obtained from a remote source, after which theimpermissible watering times may be calculated.

The lowest quartile of the values 1312 may comprise a subset of thecatch cup data 1304. The lowest quartile of the values 1312 comprise thequarter of the lowest values for the catch cups 710.

The measurement values 1314 may also comprise a subset of the catch cupdata 1304. The measurement values 1314 comprise all values indicating awater level within each catch cup 710, for example, for a particularwatering zone for a property.

The forecast evapotranspiration data 1316 indicates predictedevapotranspiration information in one or more future periods of time.The data 1316 may be obtained from a remote server sponsored by one ormore weather data providers 1252. Alternatively, the forecastevapotranspiration data 1316 may be calculated based on other types ofdata observed using one or more sensors 1240, 1238 or received from aremote server.

The forecast weather data 1320 indicates predicted weather informationin one or more future periods of time. The forecast evapotranspirationdata 1316 may comprise a subset of the forecast weather data 1320. Theforecast weather data 1320 again may be calculated or may be receivedfrom a source. The forecast weather data 1320 may comprise, for example,information related to temperature, precipitation, wind speed anddirection, barometric pressure, humidity, etc.

The forecast precipitation data 1322 indicates predicted precipitationin future periods of time. Once again, the forecast precipitation data1322 may be received from one or more weather data provider(s) 1252 ormay be calculated based on other received data or data received fromsensor(s) 1238, 1240. The forecast precipitation data 1322 may be asubset of the forecast weather data 1320.

The start time data 1324 indicates, for example, a requested start timefor sending electrical open signals to one or more associated valves1230 a-c. The start time data 1324 may also comprise not merely arequested start time but a scheduled start time. The requested starttime and the scheduled start time may be different when other factorssuggest that the requested start time, for example, does not provideadequate time for watering of one or more watering zones.

The water scheduling data 1326 comprises data identifying, for example,scheduled and/or requested start times for one or more watering zones.The water scheduling data 1326 may further comprise data indicating atotal desired watering time, total permissible watering time (if, forexample, watering restrictions are in place) for one or more zones. Thewater scheduling data 1326 may further comprise runtimes for each of theone or more watering zones and may further comprise start times for eachof the zones. The start time data 1324 and the impermissible/permissiblewatering time data 1310 may comprise a subset of the water schedulingdata 1326.

The weather data 1328 may comprise both historical weather data 1308 andforecast weather data 1320. As indicated above, the forecast weatherdata 1320 may be computed from data obtained by sensors 1238, 1240 orreceived from another source. Alternatively, the forecast weather data1320 may be received from another source without further computation.

The adjustment of in-soil water level component 1330 may adjust theestimated in-soil water level 408 when there are differences orinconsistencies between historical weather data 1308 and forecastweather data 1320. Additional information and context are provided forthis component 1330 in connection with, for example, step 1918 of FIG.19 . For example, if the forecast evapotranspiration data 1316 isinaccurate, the estimated in-soil water level 408 should be adjustedaccordingly. In various embodiments, the adjustment of in-soil waterlevel component 1330 may be configured to alter an estimated in-soilwater level 408 for a point in time based at least in part on a forecastevapotranspiration data 1316 for a period of time preceding the point intime to an altered estimated in-soil water level 408 for the point intime based at least in part on differences between the forecastevapotranspiration data 1316 for the period of time and a historicalevapotranspiration data 1306 for the period of time. The adjustment ofin-soil water level component 1330 may comprise, for example, aprocessor 1234 a-c, memory 1244 a-c, executable instructions 1246 a-c,network communications hardware 1236 a-c, sensor(s) 1240, user input(s)1242 a-c, user output(s) 1250 a-c, sensor(s) 1238, valve communicationshardware 1248 and/or computer network(s) 1204. The adjustment of in-soilwater level component 1330 may be a subset of or overlap with thein-soil water level component 1362. The adjustment of in-soil waterlevel component 1330 may, for example, communicate with and/or overlapwith the forecast evapotranspiration component 1338, the forecastprecipitation component 1342, the forecast weather component 1344, thehistorical weather component 1346, in-soil water level component 1362,the network communications component 1368, the operating component 1370,and/or the watering schedule component 1390. As used herein, the term“overlap” signifies that two or more functional components may use acommon hardware or software resources.

The average component 1332 may, in various embodiments, calculate theaverage of all measurement values for input catch cups 710. Additionalinformation and context in relation to this component 1332 are provided,for example, in connection with step 2012 of FIG. 20 . The averagecomponent 1332 may comprise, for example, a processor 1234 a-c, memory1244 a-c, executable instructions 1246 a-c, network communicationshardware 1236 a-c, sensor(s) 1238, sensor(s) 1240, user input(s) 1242a-c, user output(s) 1250 a-c, one or more routers 1202 and/or computernetwork(s) 1204. The average component 1332 may communicate with and/oroverlap with the catch cup component 1334, the lowest quartile averagecomponent 1364, the lowest quartile component 1366, a networkcommunications component 1368 and/or the valve communications component1386.

The catch cup component 1334 may, in various embodiments, utilize catchcup data 1304 to make adjustments to the watering schedule data 1326.Additional information and context regarding this component 1334 areprovided, for example, in connection with step 2010 of FIG. 20 . Invarious embodiments, the catch cup component 1334 may receive ameasurement value 1314 representing a quantity of water captured by eachcatch cup 710 within one of the watering zones during a test wateringperiod. Measurement values 1314 for the catch cups 710 may be obtainedvia a sensor 1238 or may be input manually by a user into a userinterface utilizing one or more user input(s) 1242 a-c. In variousembodiments, a catch cup component 1334 may be configured to receive oneor more measurement values 1314 representing a quantity of watercaptured by each catch cup 710 positioned within the at least onewatering zone during a test watering period and to automatically adjustthe watering schedule, without additional human intervention beyondinputting the one or more measurement values 1314, based on the one ormore measurement values 1314. The catch cup component 1334 may comprise,for example, a processor 1234 a-c, memory 1244 a-c, executableinstructions 1246 a-c, network communications hardware 1236 a-c,sensor(s) 1238, sensor(s) 1240, valve communications hardware 1248, userinput(s) 1242 a-c, user output(s) 1250 a-c, one or more routers 1202and/or computer network(s) 1204. The catch cup component 1334 may, forexample, communicate and/or overlap with the average component 1332, thelowest quartile average component 1364, estimated irrigation ratecomponent 1336, the lowest quartile component 1366, the networkcommunications component 1368 and/or the watering schedule component1390.

The estimated irrigation rate component 1336 may calculate an estimatedirrigation rate for one or more watering zones within a property.Additional information and context regarding this component 1336 areprovided, for example, in connection with step 2018 of FIG. 20 and step2220 of FIG. 22 . The estimated irrigation rate component 1336 may do sobased on data obtained from another source or from user input. Forexample, a user may specify the type of sprinkler used in connectionwith one or more of the watering zones. This information may be utilizedby the estimated irrigation rate component 1336 to determine orcalculate an estimated irrigation rate based on the irrigation rateimparted by operation of the valve associated with one of the wateringzones utilizing, for example, information related to sprinkler type.Additional information may be input or obtained, such as water pressureand velocity using one or more sensors 1238, 1240. In addition, theestimated irrigation rate component 1336 may interact with the catch cupcomponent 1334 to determine the estimated irrigation rate. In variousembodiments, the estimated irrigation rate component 1336 may calculatethe estimated irrigation rate based on the average of the lowestquartile of the values 1312 for the catch cups 710 and the average ofthe measurement values 1314 for all the catch cups 710. The estimatedirrigation rate component 1336 may comprise, for example, a processor1234 a-c, memory 1244 a-c, executable instructions 1246 a-c, networkcommunications hardware 1236 a-c, sensor(s) 1238, sensor(s) 1240, valvecommunications hardware 1248, user input(s) 1242 a-c, user output(s)1250 a-c, one or more routers 1202 and/or computer network(s) 1204. Theestimated irrigation rate component 1336 may, for example, communicateand/or overlap with the catch cup component 1334, lowest quartileaverage component 1364, lowest quartile component 1366, networkcommunications component 1368 and/or with watering schedule component1390.

The forecast evapotranspiration component 1338 may calculate or receiveevapotranspiration data 1316 based on forecast weather data 1320, aswill be explained in further detail, for example, in connection withstep 1716 of FIG. 17 , step 2022 of FIG. 20 , and step 2214 of FIG. 22 .The forecast evapotranspiration data 1316 may be received utilizing thenetwork communications component 1368. In addition or alternatively,data may be received from the sensors 1238, 1240 or based on user input,which may be utilized to calculate the forecast evapotranspiration data1316 utilizing the forecast evapotranspiration component 1338 and/orforecast weather data 1320. The forecast evapotranspiration component1338 may comprise, for example, a processor 1234 a-c, memory 1244 a-c,executable instructions 1246 a-c, network communications hardware 1236a-c, sensor(s) 1238, sensor(s) 1240, valve communications hardware 1248,user input(s) 1242 a-c, user output(s) 1250 a-c, one or more routers1202 and/or computer network(s) 1204. The forecast evapotranspirationcomponent 1338 may, for example, communicate and/or overlap with theforecast weather component 1344, the in-soil water level component 1362,the network communications component 1368 and/or the watering schedulecomponent 1390.

The future permissible watering time periods component 1340 may identifypermissible watering periods within a future temporal period. Additionalinformation and context regarding this component 1340 are provided, forexample, in connection with step 2114 of FIG. 21 . The futurepermissible watering time periods component 1340 may utilizeimpermissible/permissible watering time data 1310 which may be receivedfrom a source via a server or may be input by a user utilizing one ormore user input(s) 1242 a-c. The future permissible watering timeperiods component 1340 may comprise, for example, a processor 1234 a-c,memory 1244 a-c, executable instructions 1246 a-c, networkcommunications hardware 1236 a-c, user input(s) 1242 a-c, user output(s)1250 a-c, one or more routers 1202 and/or computer network(s) 1204. Thefuture permissible watering time periods component 1340 may, forexample, communicate and/or overlap with the impermissible periodidentification component 1348, network communications component 1368,the nearest identification component 1350, the time computationcomponent 1352 and/or a total permissible watering time component 1384.

The forecast precipitation component 1342 may receive forecastprecipitation data 1322 for at least one watering zone, as will beexplained in further detail, for example, in connection with step 2216of FIG. 22 and step 2316 of FIG. 23 . The forecast precipitationcomponent 1342 may comprise, for example, a processor 1234 a-c, memory1244 a-c, executable instructions 1246 a-c, network communicationshardware 1236 a-c, user output(s) 1250 a-c, one or more routers 1202and/or computer network(s) 1204. The forecast precipitation component1342 may, for example, communicate and/or overlap with the forecastweather component 1344 and/or the watering schedule component 1390.

The forecast weather component 1344 may receive forecast precipitationdata 1322 for at least one watering zone for a period of time, as willbe explained in further detail, for example, in connection with step2024 of FIG. 20 . In addition, the forecast weather component 1344 mayutilize information received via one or more user input(s) 1242 a-c orsensors 1238, 1240 to formulate a weather forecast. The forecast weathercomponent 1344 may comprise, for example, a processor 1234 a-c, memory1244 a-c, executable instructions 1246 a-c, network communicationshardware 1236 a-c, sensor(s) 1238, sensor(s) 1240, user input(s) 1242a-c, user output(s) 1250 a-c, one or more routers 1202 and/or computernetwork(s) 1204. The forecast weather component 1344 may, for example,communicate and/or overlap with the adjustment of in-soil water levelcomponent 1330, the forecast evapotranspiration component 1338, theforecast precipitation component 1342, the historical weather component1346, the network communications component 1368 and/or the wateringschedule component 1390.

The historical weather component 1346 may obtain historical weather data1308 for a particular period of time, as will be explained in furtherdetail in connection with step 1916 of FIG. 19 . The historical weathercomponent 1346 may obtain the historical weather data 1308 from theserver, user input(s) 1242 a-c and one or more sensors 1238, 1240. Thehistorical weather component 1346 may comprise, for example, a processor1234 a-c, memory 1244 a-c, executable instructions 1246 a-c, networkcommunications hardware 1236 a-c, sensor(s) 1238, sensor(s) 1240, userinput(s) 1242 a-c, one or more routers 1202 and/or computer network(s)1204. The historical weather component 1346 may, for example,communicate and/or overlap with the adjustment of in-soil water levelcomponent 1330 and/or the network communications component 1368.

The impermissible period identification component 1348 may identify oneor more impermissible periods of time within a temporal period whenirrigation is impermissible based on impermissible/permissible wateringtime data 1310, as will be explained in further detail in connectionwith step 1810 of FIG. 18 . The impermissible period identificationcomponent 1348 may perform this task using solely data 1302 or userinput received or may perform computations based on data or user inputreceived to identify when irrigation is impermissible. Impermissibleperiod identification component 1348 may comprise, for example, aprocessor 1234 a-c, memory 1244 a-c, executable instructions 1246 a-c,network communications hardware 1236 a-c, user input(s) 1242 a-c, one ormore routers 1202 and/or computer network(s) 1204. The impermissibleperiod identification component 1348 may, for example, communicateand/or overlap with the future permissible watering time periodscomponent 1340, the network communications component 1368 the nearestidentification component 1350, the time computation component 1352and/or the total permissible watering time component 1384.

The nearest identification component 1350 may identify the permissiblewatering period nearest a requested start time or that encompassed therequested start time, as will be explained in further detail inconnection with step 2116 of FIG. 21 . The nearest identificationcomponent 1350 may identify the nearest permissible watering period tothe requested start time or any permissible watering period thatencompasses the requested start time using, for example, start time data1324 and/or impermissible/permissible watering time data 1310. Theimpermissible/permissible watering time data 1310 may be input by a useror received from another source, such as a remote server. The nearestidentification component 1350 may comprise, for example, a processor1234 a-c, memory 1244 a-c, executable instructions 1246 a-c, networkcommunications hardware 1236 a-c, user input(s) 1242 a-c, user output(s)1250 a-c, one or more routers 1202 and/or computer network(s) 1204. Thenearest identification component 1350 may, for example, communicateand/or overlap with the requested start time component 1374, the totaldesired watering time component 1380, the future permissible wateringtime periods component 1340, impermissible period identificationcomponent 1348, the total permissible watering time component 1384, thetime computation component 1352, the start watering time adjustmentcomponent 1376 and/or the watering schedule component 1390.

The time computation component 1352 may calculate the time within thenearest permissible watering period (identified by the nearestidentification component 1350) after the requested start time, as willbe explained in further detail in connection with step 2117 of FIG. 21 .To state it a different way, the time computation component 1352calculates the time that is (1) within the nearest permissible wateringperiod, and (2) after the requested start time. The time computationcomponent 1352 may do so, for example, using start time data 1324 and/orimpermissible/permissible watering time data 1310. The time computationcomponent 1352 may comprise, for example, a processor 1234 a-c, memory1244 a-c, executable instructions 1246 a-c, network communicationshardware 1236 a-c, user input(s) 1242 a-c, user output(s) 1250 a-c, oneor more routers 1202 and/or computer network(s) 1204. The timecomputation component 1352 may, for example, communicate and/or overlapwith the requested start time component 1374, the total desired wateringtime component 1380, the future permissible watering time periodscomponent 1340, impermissible period identification component 1348, thetotal permissible watering time component 1384, the nearestidentification component 1350, the start watering time adjustmentcomponent 1376, and/or the watering schedule component 1390.

The in-soil water capacity component 1360 may identify an estimatedin-soil water capacity 420 for soil for one or more watering zones on aproperty, as will be explained in additional detail in connection withstep 1710 of FIG. 17 , step 2026 of FIG. 20 , step 2212 of FIG. 22and/or step 2312 of FIG. 23 . As noted above, the in-soil water capacity420 may be referred to as field capacity. The in-soil water capacitycomponent 1360 may do so based on, for example, user input specifying asoil type. In addition, a default soil type may be utilized if no userinput is received. Alternatively, a likely soil type may be determinedby this component 1360 using GPS data or zip code data. The in-soilwater capacity component 1360 may comprise, for example, a processor1234 a-c, memory 1244 a-c, executable instructions 1246 a-c, networkcommunications hardware 1236 a-c, user input(s) 1242 a-c, user output(s)1250 a-c, one or more routers 1202 and/or computer network(s) 1204. Invarious embodiments, the in-soil water capacity component 1360 mayestimate in-soil water capacity for at least one watering zone based atleast in part on user input specifying a soil type for the at least onewatering zone. The in-soil water capacity component 1360 may, forexample, communicate and/or overlap with the network communicationscomponent 1368 and/or watering schedule component 1390.

The in-soil water level component 1362 may ascertain an estimated futureor current in-soil water level 408, as will be explained in additionaldetail, for example, in connection with step 1712 of FIG. 17 , steps1910 and 1914 of FIG. 19 , steps 2020 and 2026 of FIG. 20 , and steps2210 and 2218 of FIG. 22 , and steps 2310 and 2318 of FIG. 23 . Thein-soil water level component 1362 may estimate in-soil water level 408based on a number of different factors, including, for example,historical evapotranspiration data 1306, soil-type data, historicalweather data 1308, forecast evapotranspiration data 1316, forecastweather data 1320, forecast precipitation data 1322 and other weatherdata 1328. The in-soil water level component 1362 may comprise, forexample, a processor 1234 a-c, memory 1244 a-c, executable instructions1246 a-c, sensor(s) 1240, user input(s) 1242 a-c, user output(s) 1250a-c and/or sensor(s) 1238. The in-soil water level component 1362 mayemploy historical evapotranspiration data 1306, historical weather data1308, forecast evapotranspiration data 1316, forecast weather data 1320,forecast precipitation data 1322, and/or water scheduling data 1326. Thein-soil water level component 1362 may interact with and/or overlap withthe adjustment of in-soil water level component 1330, forecastevapotranspiration component 1338, forecast precipitation component1342, forecast weather component 1344, historical weather component1346, network communications component 1368 and/or watering schedulecomponent 1390.

The lowest quartile average component 1364 may calculate an average ofthe measurement values within the lowest quartile of the values 1312 ofcatch cups 710 for a particular test watering period, as will beexplained in additional detail in connection with step 2016 of FIG. 20 .The measurement values 1314 for each catch cup 710, as indicated above,may be obtained via user input(s) 1242 a-c or via sensor(s) 1238, 1240.The lowest quartile average component 1364 may comprise, for example, aprocessor 1234 a-c, memory 1244 a-c, executable instructions 1246 a-c,network communications hardware 1236 a-c, sensor(s) 1238, sensor(s)1240, valve communications hardware 1248, user input(s) 1242 a-c, useroutput(s) 1250 a-c, one or more routers 1202 and/or computer network(s)1204. The lowest quartile average component 1364 may, for example,communicate and/or overlap with the average component 1332, the catchcup component 1334, the lowest quartile component 1366, the networkcommunications component 1368 and/or the estimated irrigation ratecomponent 1336.

The lowest quartile component 1366 may identify one or more measurementvalues 1314 for catch cups 710 falling within the lowest quartile of thevalues 1312 based on the catch cup data 1304 and/or measurement values1314. Additional information and context regarding this component 1366are provided, for example, in connection with step 2014 of FIG. 20 . Thelowest quartile component 1366 may comprise, for example, a processor1234 a-c, memory 1244 a-c, executable instructions 1246 a-c, networkcommunications hardware 1236 a-c, user input(s) 1242 a-c, user output(s)1250 a-c, one or more routers 1202 and/or computer network(s) 1204. Thelowest quartile component 1366 may, for example, communicate and/oroverlap with the average component 1332, the catch cup component 1334,the lowest quartile average component 1364, the network communicationscomponent 1368, and/or the estimated irrigation rate component 1336.

The network communications component 1368 may be utilized forcommunicating with other devices in communication with the computernetwork(s) 1204. The network communications component 1368 may comprise,for example, a processor 1234 a-c, memory 1244 a-c, executableinstructions 1246 a-c, network communications hardware 1236 a-c, one ormore routers 1202 and/or computer network(s) 1204. The networkcommunications component 1368 may communicate and/or overlap with manyof the other components identified in the FIGS. 13A-B, including, forexample, the forecast evapotranspiration component 1338, the futurepermissible watering time periods component 1340, the forecastprecipitation component 1342, the forecast weather component 1344, thehistorical weather component 1346 and/or the impermissible periodidentification component 1348.

The operating component 1370 may operate the sprinkler controller inaccordance with a watering schedule, which may be based on and specifiedby watering schedule data 1326. Additional information and contextregarding this component 1370 are provided, for example, in connectionwith step 1726 of FIG. 17 , step 1820 of FIG. 18 and/or step 2124 ofFIG. 21 . The operating component may, for example, transmit electricalsignals to open or close irrigation valves 1230 a-c using valvecommunications hardware 1248, which may include one or more TRIACs. Theoperating component 1370 may comprise, for example, a processor 1234a-c, memory 1244 a-c, executable instructions 1246 a-c, networkcommunications hardware 1236 a-c, valve communications hardware 1248,user input(s) 1242 a-c, user output(s) 1250 a-c, one or more routers1202 and/or computer network(s) 1204. The operating component 1370 may,for example, communicate and/or overlap with the valve communicationscomponent 1386 and/or the watering schedule component 1390.

The replenishment point component 1371 may calculate a replenishmentpoint level 425 for the at least one watering zone within a property, aswill be explained in additional detail, for example, in connection withstep 1714 of FIG. 17 . As noted above, the replenishment point level 425may be computed based on various factors, including soil type and rootzone depth 410. These factors affecting a replenishment point level 425may be input by a user or may be received from a remote source. Thereplenishment point component 1371 may comprise, for example, aprocessor 1234 a-c, memory 1244 a-c, executable instructions 1246 a-c,network communications hardware 1236 a-c, sensor(s) 1238, sensor(s)1240, valve communications hardware 1248, user input(s) 1242 a-c, useroutput(s) 1250 a-c, one or more routers 1202 and/or computer network(s)1204. The replenishment point component 1371 may, for example,communicate and/or overlap with the replenishment point time component1372 and/or the watering schedule component 1390.

The replenishment point time component 1372 may calculate, based atleast in part on the forecast evapotranspiration data 1316, an estimatedreplenishment point time when the estimated in-soil water level 408 willreach or extend below the replenishment point level 425 within the atleast one watering zone, as will be explained in further detail inconnection with, for example, step 1718 of FIG. 17 . In variousembodiments, the replenishment point time indicates the estimated time(based, for example, on forecast evapotranspiration data 1316, forecastweather data 1320, the estimated in-soil water level 408) when theestimated in-soil water level 408 will reach or extend below thereplenishment point level 425. In various embodiments, the estimatedreplenishment point time component may utilize the equation in row no.(3) of Table 8 herein. The replenishment point time component 1372 maycomprise, for example, a processor 1234 a-c, memory 1244 a-c, executableinstructions 1246 a-c, network communications hardware 1236 a-c,sensor(s) 1238, sensor(s) 1240, user input(s) 1242 a-c, user output(s)1250 a-c, one or more routers 1202 and/or computer network(s) 1204. Thereplenishment point time component 1372 may, for example, communicateand/or overlap with the replenishment point component 1371 and/orwatering schedule component 1390.

The requested start time component 1374 may receive user inputspecifying a requested start time for at least one watering zone, aswill be explained in further detail in connection with step 2110 of FIG.21 . Various types of user interfaces may be presented to a user inaccordance with the foregoing. For example, a user may be asked toinput, using text-to-speech technology, a requested start time at anend-user device 1200 c, 1600 c. Employing voice recognition technology,user input in the form of a user’s voice may be received to indicate arequested start time. Of course, other types of user interfaces may beemployed to receive the requested start time for a particular wateringzone. The requested start time component 1374 may comprise, for example,a processor 1234 a-c, memory 1244 a-c, executable instructions 1246 a-c,network communications hardware 1236 a-c, sensor(s) 1238, sensor(s)1240, user input(s) 1242 a-c, user output(s) 1250 a-c, one or morerouters 1202 and/or computer network(s) 1204. The requested start timecomponent 1374 may, for example, communicate and/or overlap with futurepermissible watering time periods component 1340, network communicationscomponent 1368, the requested start time component 1374 and/or startwatering time adjustment component 1376.

The start watering time adjustment component 1376 may, if a computedtime (i.e., the time (1) after the start time and (2) within the nearestpermissible watering period) is less than the total desired run time,move the start time (which may be specified by start time data 1324)backward or forward in time relative to the requested start time toincrease the total permissible watering time. Additional information andcontext regarding this component 1376 are provided, for example, inconnection with steps 2118, 2120 and 2123 of FIG. 21 . In one or moreembodiments, the start watering time adjustment component 1376 may movea requested start time for watering specified by user input backward orforward in time to increase a total permissible watering time before animpermissible watering period, as explained more fully, for example, inconnection with the method 2100 of FIG. 21 . In various embodiments, thestart watering time adjustment component 1376 may move a requested starttime (e.g., a start time requested by a user) backward or forward intime to allow for additional time to water one or more zones of theproperty. In various embodiments, a start watering time adjustmentcomponent 1376 be configured to move a start time for watering away froma user-requested start time based on an analysis of permissible andimpermissible watering periods (which may be based onpermissible/impermissible watering time data 1310). The start wateringtime adjustment component 1376 may comprise, for example, a processor1234 a-c, memory 1244 a-c, executable instructions 1246 a-c, networkcommunications hardware 1236 a-c, user input(s) 1242 a-c, user output(s)1250 a-c, one or more routers 1202 and/or computer network(s) 1204. Thestart watering time adjustment component 1376 may, for example,communicate and/or overlap with the network communications component1368, the requested start time component 1374, the nearestidentification component 1350, the time computation component 1352and/or the total desired watering time component 1380.

The total desired watering time component 1380 may calculate a totaldesired watering time (sometimes referred to, for example, as a “totaldesired run time” or “total ideal run time”) equal to a sum of desiredwatering times (sometimes referred to, for example, as “run time”) foreach of the watering zones within the future temporal period. Thecomputations of the total desired watering time component 1380 may bebased, for example, on forecast weather data 1320. Additionalinformation and context regarding this component 1380 are provided, forexample, in connection with step 512 of FIG. 5 , step 1814 of FIG. 18and/or step 2112 of FIG. 21 . A desired watering time indicates awatering time for a zone to achieve a particular watering objective(which objective may vary depending upon the particular implementation)when there are no watering restrictions. The total desired watering timecomponent 1380 may comprise, for example, a processor 1234 a-c, memory1244 a-c, executable instructions 1246 a-c, network communicationshardware 1236 a-c, user input(s) 1242 a-c, user output(s) 1250 a-c, oneor more routers 1202 and/or computer network(s) 1204. The total desiredwatering time component 1380 may, for example, communicate and/oroverlap with a requested start time component 1374, the futurepermissible watering time periods component 1340, the total permissiblewatering time component 1384, the start watering time adjustmentcomponent 1376, the watering schedule component 1390, the nearestidentification component 1350, the time computation component 1352and/or the operating component 1370.

The total scheduled watering time component 1382 may, without humanintervention, calculate a scheduled watering time for the at least onewatering zone based at least in part on a ratio between the lowestquartile average (the average of the lowest quartile of values 1312 forcatch cups 710) and the average of the measurement values 1314 for allof the catch cups 710 used during a test watering period. Additionalinformation and context regarding this component 1382 are provided, forexample, at step 2028 of FIG. 20 . The total scheduled watering timecomponent 1382 may comprise, for example, a processor 1234 a-c, memory1244 a-c, executable instructions 1246 a-c, network communicationshardware 1236 a-c, user input(s) 1242 a-c, user output(s) 1250 a-c,valve communications hardware 1248, one or more routers 1202 and/orcomputer network(s) 1204. The total scheduled watering time component1382 may, for example, communicate and/or overlap with the averagecomponent 1332, the lowest quartile component 1366 and/or the lowestquartile average component 1364.

The total permissible watering time component 1384 may calculate thetotal permissible watering time within a temporal period after the starttime specified by the start time data 1324. The total permissiblewatering time is the time within the temporal period outside of anyimpermissible watering times. The total permissible watering timecomponent 1384 may do so by communication with other components and/ordevices via the computer network(s) 1204 or using data stored within thedevice performing the operation. Additional information and contextregarding this component 1384 are provided, for example, in connectionwith step 1812 of FIG. 18 . The total permissible watering timecomponent 1384 may comprise, for example, a processor 1234 a-c, memory1244 a-c, executable instructions 1246 a-c, network communicationshardware 1236 a-c, user input(s) 1242 a-c, user output(s) 1250 a-c, oneor more routers 1202 and/or computer network(s) 1204. The totalpermissible watering time component 1384 may, for example, communicateand/or overlap with the requested start time component 1374, the totaldesired watering time component 1380, the future permissible wateringtime periods component 1340, the start watering time adjustmentcomponent 1376 the nearest identification component 1350, the timecomputation component 1352 and/or the watering schedule component 1390.

The valve communications component 1386 may transmit electrical signalsto one or more of the valves 1230 a-c to open or close the one or morevalves. The valve communications component 1386 may comprise, forexample, a processor 1234 a-c, memory 1244 a-c, executable instructions1246 a-c and/or valve communications hardware 1248, one or more routers1202 and/or computer network(s) 1204. The valve communications component1386 may, for example, communicate and/or overlap with the wateringschedule component 1390.

The water level difference component 1388 may identify a differencebetween an estimated in-soil water level 408 and the estimated in-soilwater capacity 420 for at least one watering zone. Additionalinformation and context regarding this component 1388 are provided, forexample, in connection with step 2222 of FIG. 22 . The water leveldifference component 1388 may comprise, for example, a processor 1234a-c, memory 1244 a-c, executable instructions 1246 a-c, networkcommunications hardware 1236 a-c, sensor(s) 1238, sensor(s) 1240, 1240,user input(s) 1242 a-c, user output(s) 1250 a-c, valve communicationshardware 1248, one or more routers 1202 and/or computer network(s) 1204.Water level difference component 1388 may, for example, communicateand/or overlap with the forecast evapotranspiration component 1338, theforecast precipitation component 1342, the estimated irrigation ratecomponent 1336, the in-soil water level component 1362, the in-soilwater capacity component 1360 and/or the watering schedule component1390.

The watering schedule component 1390 may formulate a watering schedulebased on watering schedule data 1326. The watering schedule component1390 may consider a number of factors, such as the position of thein-soil water level 408 for a weight relative to the replenishment pointlevel 425, catch cup data 1304, the total permissible watering timerelative to the total desired watering time, a requested start time(which may comprise a portion of the start time data 1324) and/orupcoming impermissible watering periods. Additional information andcontext regarding this component 1390 are provided, for example, inconnection with steps 1722, 1724 and 1726 of FIG. 17 , steps 1816, 1818and 1820 of FIG. 18 , step 2030 of FIG. 20 , steps 2122 and 2123 of FIG.21 , step 2224 of FIG. 22 . The watering schedule component 1390 maycomprise, for example, a processor 1234 a-c, memory 1244 a-c, executableinstructions 1246 a-c, network communications hardware 1236 a-c,sensor(s) 1238, sensor(s) 1240, user input(s) 1242 a-c, user output(s)1250 a-c, valve communications hardware 1248, one or more routers 1202and/or computer network(s) 1204. The watering schedule component 1390may, for example, communicate and/or overlap each of the componentsidentified in FIGS. 13A-B and 14-16 .

The watering time compression component 1392 is configured toproportionally reduce an actual watering time for each watering zonewithin the property if a total desired watering time for all of thewatering zones exceeds a total permissible watering time within atemporal period. Additional information and context regarding thiscomponent 1392 are provided, for example, in connection with method 2100of FIG. 21 . The watering time compression component 1392 may comprise,for example, a processor 1234 a-c, memory 1244 a-c, executableinstructions 1246 a-c, network communications hardware 1236 a-c,sensor(s) 1238, sensor(s) 1240, user input(s) 1242 a-c, user output(s)1250 a-c, valve communications hardware 1248, one or more routers 1202and/or computer network(s) 1204. The watering time compression component1392 may, for example, communicate and/or overlap with the impermissibleperiod identification component 1348, the total permissible wateringtime component 1384, the total desired watering time component 1380and/or watering schedule component 1390.

The current settings component 1394 may obtain current settings for anirrigation controller. In various embodiments, the current settingscomponent 1394 may obtain the current settings from a remotely locatedirrigation controller via one or more computer networks 1204. Forexample, a server 1500 b and/or an end-user device 1600 c may obtaincurrent settings for a local device 1400 a via one or more computernetworks 1204. Additional information and context regarding thiscomponent 1394 are provided, for example, in connection with step 2320of FIG. 23 . The current settings component 1394 may comprise, forexample, a processor 1234 a-c, memory 1244 a-c, executable instructions1246 a-c, network communications hardware 1236 a-c, user input(s) 1242a-c, user output(s) 1250 a-c, one or more routers 1202 and/or computernetwork(s) 1204. The current settings component 1394 may, for example,communicate and/or overlap with the current settings component 1394, thein-soil water level component 1362, in-soil water capacity component1360, the forecast evapotranspiration component 1338, the forecastprecipitation component 1342, the watering schedule component 1390, therecommended changes component 1396 and/or notification component 1398.

The recommended changes component 1396 may formulate a set of one ormore recommended changes for the watering schedule component 1390 of anirrigation controller. The recommended changes component 1396 mayoperate and reside on a device remote from a local device 1400 a, suchas on a server 1500 b and/or an end-user device 1600 c. Additionalinformation and context regarding this component 1396 are provided, forexample, in connection with step 2322 of FIG. 23 . The recommendedchanges component 1396 may comprise, for example, a processor 1234 a-c,memory 1244 a-c, executable instructions 1246 a-c, networkcommunications hardware 1236 a-c, user input(s) 1242 a-c, user output(s)1250 a-c, valve communications hardware 1248, one or more routers 1202and/or computer network(s) 1204. The recommended changes component 1396may, for example, communicate and/or overlap with the current settingscomponent 1394, the in-soil water level component 1362, in-soil watercapacity component 1360, the forecast evapotranspiration component 1338,the forecast precipitation component 1342, the watering schedulecomponent 1390 and/or notification component 1398.

The notification component 1398 may transmit or present electronicnotification of a set of one or more recommended changes to the wateringschedule. The electronic notification may be formulated into a userinterface which may be viewed by a user on, for example, a local device1400 a, a server 1500 b, and/or an end-user device 1600 c. Additionalinformation and context regarding this component 1398 are provided, forexample, in connection with step 2324 of FIG. 23 . The notificationcomponent 1398 may comprise, for example, a processor 1234 a-c, memory1244 a-c, executable instructions 1246 a-c, network communicationshardware 1236 a-c, user input(s) 1242 a-c, user output(s) 1250 a-c,valve communications hardware 1248, one or more routers 1202 and/orcomputer network(s) 1204. The notification component 1398 may, forexample, communicate and/or overlap with the current settings component1394, the in-soil water level component 1362, in-soil water capacitycomponent 1360, the forecast evapotranspiration component 1338, theforecast precipitation component 1342, the watering schedule component1390 and/or the recommended changes component 1396.

It should be noted that the functional components identified in FIGS.13A-B, 14A-B, 15A-B, and 16A-B may operate on one or more of the localdevice 1400 a, the server 1500 b, and/or the end-user device 1600 c. Invarious embodiments, each of the local device 1400 a, the server 1500 b,and/or the end-user device 1600 c may perform all or a portion of theidentified functions. Accordingly, the disclosed subject matterencompasses computations and operations performed by a single device anda group of devices.

Referring now to FIGS. 17-23 , the illustrated methods may be practiced,for example, using the multi-zone irrigation controller 100 of FIG. 1 ,the hose faucet irrigation controller 200 of FIG. 2 , the irrigationcontroller 300 of FIG. 3 , the irrigation controller 1200 or localdevice 1200 a of FIG. 12A, the server 1200 b of FIG. 12B, the end-userdevice 1200 c of FIG. 12C, the irrigation controller 1300 of FIGS.13A-B, the local device 1400 a of FIGS. 14A-B, the server 1500 b ofFIGS. 15A-B, the end-user device 1600 c of FIGS. 16A-B and/or any othersystem or device within the scope of the present disclosure. Moreover,the method 1700 may be implemented by one or more processors and memoryassociated with any system or device within the scope of the presentdisclosure, such as the memory 1244 a-c and processors 1234 a-cillustrated in FIGS. 12A-C.

With reference now to FIG. 17 , a flowchart is shown of a method 1700for formulating a watering schedule based at least in part on anestimated replenishment point level 425. The method 1700 may begin withstep 1710 in which an estimated in-soil water capacity 420 may becalculated for at least one watering zone by an in-soil water capacitycomponent 1360. The estimated in-soil water capacity 420 may becalculated based on the type of soil in the watering zone (e.g., sandysoil, loam soil, clay soil, etc.). The type of soil may be a defaulttype of soil in general (or for a specific area based on GPS coordinatesor ZIP Code) or, alternatively, may be specified through user input.Alternatively and/or additionally, the estimated in-soil water capacity420 may be obtained from an external source (for example, from a serveror from memory) which may be based on or provided by a look-up table, agovernmental agency, or any other external source that tracks theestimated in-soil water capacity 420 for soils in an area.Alternatively, the estimated in-soil water capacity 420 may be directlymeasured by any known technique in the art, and/or may be calculated forthe at least one watering zone, based at least in part on user inputspecifying a soil type for the at least one watering zone.

In step 1712, an estimated in-soil water level 408 may be calculated forthe at least one watering zone by an in-soil water level component 1362.The estimated in-soil water level 408 may be calculated based onprior/historical irrigation, precipitation, evapotranspiration, andweather data. Alternatively, the estimated in-soil water level 408 maybe calculated, for example, using historical evapotranspiration data1306 and other historical weather data 1308. As used herein, the term“calculate” may encompass direct measurement of the in-soil water level408 through, for example, use of a sensor 1238.

In step 1714, a replenishment point level 425 may be calculated for theat least one watering zone by a replenishment point component 1371. Thereplenishment point level 425 may be calculated, for example, based onthe type of plants in the at least one watering zone, the root zonedepth 410 of the plants, the type of soil, and the estimated in-soilwater capacity 420 of the soil. Alternatively, the replenishment pointlevel 425 may be chosen based on known measurements of similarsoils/plants to estimate an appropriate replenishment point level 425.

In step 1716, forecast evapotranspiration data 1316 may be calculated orreceived by a forecast evapotranspiration component 1338 for the atleast one watering zone. In various embodiments, the forecastevapotranspiration component 1338 may calculate the forecastevapotranspiration data 1316 based at least in part on forecast weatherdata 1320. Forecast weather data 1320 may include forecast temperaturedata, forecast humidity data, forecast wind data and the like. Theforecast evapotranspiration data 1316 may comprise or utilize thelandscape evapotranspiration rate (“Landscape ET”) referenced in Table5.

In step 1718, a replenishment point time may be calculated by areplenishment point time component 1372 for the at least one wateringzone. In various embodiments, the replenishment point time may be basedat least in part on the forecast evapotranspiration data 1316. Invarious embodiments, the equation provided in row no. (3) of Table 8 maybe utilized to calculate the replenishment point time. It should benoted that other equations may be employed to ascertain thereplenishment point time.

In step 1720, a determination of whether a replenishment point time isestimated to occur within a permissible watering period may be made.Should the replenishment point time occur within a permissible wateringperiod, the method 1700 may proceed to step 1722. Alternatively, shouldthe replenishment point time be estimated to not occur within apermissible watering period, the method 1700 may proceed to step 1724.

In step 1722, a watering schedule may be formulated by a wateringschedule component 1390 in which watering is scheduled within thepermissible watering period until the estimated in-soil water level 408reaches the estimated in-soil water capacity 420 or until thepermissible period ends. Thus, the watering schedule may scheduleelectric signals to be sent to open the one or more irrigation valvesassociated with the at least one watering zone. In this manner, theformulated watering schedule may allow the estimated in-soil water level408 to reach the estimated in-soil water capacity 420 in the conditionsenumerated above.

In step 1724, a watering schedule may be formulated in which watering isscheduled within a prior permissible watering period immediately beforethe impermissible watering period until the estimated in-soil waterlevel 408 reaches the estimated in-soil water capacity 420 or until theprior permissible watering period ends, or within a subsequentpermissible watering period immediately after the impermissible wateringperiod until the estimated in-soil water level 408 reaches the estimatedin-soil water capacity 420 or until the subsequent permissible wateringperiod ends. Thus, the formulated watering schedule may allow theestimated in-soil water level 408 to reach the estimated in-soil watercapacity 420 while not watering within any impermissible wateringperiods.

In step 1726, the sprinkler controller may be operated in accordancewith the formulated watering schedule obtained from step 1722 or step1724 by an operating component 1370.

Referring now to FIG. 18 , a flowchart is shown of a method 1800 forformulating a watering schedule based on one or more impermissiblewatering periods. As shown, the method 1800 may begin with step 1810 inwhich one or more impermissible periods of time for watering areidentified based on impermissible/permissible watering time data 1310received by an impermissible period identification component 1348. Theone or more impermissible periods of time may be instituted by a watermanagement company, agency, government, or the like in order to helpconserve water. Impermissible periods of time may include certain timesof the day (e.g., during the hottest times of the day whenevapotranspiration is high) or may last for entire days or any otherperiod of time.

In step 1812, a total permissible time for watering within the temporalperiod, outside of the one or more impermissible periods of time, isdetermined by a total permissible watering time component 1384.

In step 1814, a total desired time for watering the property during thetemporal period based, at least in part, on forecast weather data 1320for the property is determined by a total desired watering timecomponent 1380.

In step 1816, a determination of whether the total desired time forwatering is more than the total permissible time is made by a wateringschedule component 1390. If the total desired time for watering is morethan the total permissible time, the method 1800 may proceed to step1818. Alternatively, if the total desired time for watering is less than(or equal to) the total permissible time, the method 1800 may proceed tostep 1820.

In step 1818, the watering schedule component 1390 may proportionallyreduce a total watering time (or actual watering time) within thewatering schedule for each zone by a watering time compression component1392, or alternatively, the watering schedule component 1390 may reducea watering time for at least one zone based on the greatest estimatedin-soil water levels 408 such that the total watering time is less thanor equal to the total permissible time.

In step 1820, an operating component 1370 may operate the sprinklercontroller in accordance with the formulated watering schedule.

Referring now to FIG. 19 , a flowchart is shown of a method 1900 forupdating an estimated in-soil water level 408 based on historicalweather data 1308. The method 1900 may begin with step 1910 in which afirst estimated in-soil water level 408 for at least one watering zoneon the property at a first point in time may be calculated by an in-soilwater level component 1362, as previously discussed with reference toFIG. 17 .

In step 1912, forecast evapotranspiration data 1316 for the at least onewatering zone during the intermediate period of time may be calculatedor received by a forecast evapotranspiration component 1338. Theforecast evapotranspiration data 1316 may be based at least in part onforecast weather data 1320 for an intermediate period of time extendingbetween the first point in time and a subsequent, second point in time.

In step 1914, a second estimated in-soil water level 408 for the atleast one watering zone on the property at the second point in time maybe calculated by the in-soil water level component 1362. The secondestimated in-soil water level 408 may also be based at least in part onthe forecast evapotranspiration data 1316.

In step 1916, historical weather data 1308 after the second point intime for the intermediate period of time may be obtained by a historicalweather component 1346.

In step 1918, the second estimated in-soil water level 408 at the secondpoint in time may be altered by the adjustment of in-soil water levelcomponent 1330 in accordance with differences or inconsistencies betweenthe forecast weather data 1320 and the historical weather data 1308.

Furthermore, in at least one embodiment, the watering schedule may beadjusted based on the altered second estimated in-soil water level 408.In various embodiments, the estimated in-soil water level 408 may beadjusted or corrected when historical weather data 1308 is inconsistentwith forecast weather data 1320. In another embodiment, an estimatedin-soil water level 408 for a point in time may be altered based atleast in part on a forecast evapotranspiration data 1316 for a period oftime preceding the point in time to an altered estimated in-soil waterlevel 408 for the point in time based at least in part on differences orinconsistencies between the forecast evapotranspiration data 1316 forthe period of time and a historical evapotranspiration data 1306 for theperiod of time.

Referring now to FIG. 20 , a flowchart is shown of a method 2000 forformulating a watering schedule based on a lowest quartile average ofmeasurement values 1314 for the catch cups 710.

Table 5 below illustrates data, information, equations and variables,along with their associated sample values, units, and explanations whichmay be employed, in various embodiments, to carry out one or more stepsof the method 2000 of FIG. 20 . The information, sample values, units,and explanations identified in Table 5 are only exemplary and are notlimiting of the manner in which the method 2000 may be implemented.

Table 5 is as follows:

TABLE 5 No. Name Sample Value Units Explanation (1) Zip Code 84010 Nounits Input by user or obtained from GPS on local device 300 a, 1200 a,or 1400 a or an associated end-user device 300 c, 1200 c, or 1600 c (2)Testing Run Time for Catch Cups 710 5 Minutes The use of catch cup datameasurement values 1314 is optional; this value may be input by a useror a default value may be used (3) Soil Texture Class Clay No units Thedefault value may be loam or may, alternatively, be selected by a userfrom various options, including clay, clay loam, loam, sandy loam andsandy (4) Root Zone Depth 410 6 Inches The default value may be 6 inchesor may alternatively be specified through user input (5) Days in EToReference Period 31 Days Obtained from a calendar and indicates thenumber of days in a current month (6) Reference ET_(o) 8.39 Inches /month Reference Evapotranspiration from, for example, the InternationalWater Management Institute (IWMI) tables and may be based on ZIP Codeand calendar / time (7) Landscape Coefficient (K_(L)) 70% Percent Thisvalue may employ, for example, a default value of 70 percent and takeinto account and may be adjusted, for example, based on plant species,microclimate (the climate in a particular area), and plant density. Thisvalue may be calculated by the irrigation controller based on userinputs related, for example, to plant type, plant density and / or ZIPCode, or may be received / obtained from another system (such as theserver 300 b, 1200 b, 1500 b) or entity. (8) Landscape ET 5.87 Inches[Reference ET_(o)] * [Landscape Coefficient (K_(L))] This can also bereferred to as ET_(c) (Crop ET) or the landscape evapotranspiration rate(9) Average Daily ET_(o) 0.19 Inches / day [Landscape ET_(c)] / [ET_(o)Reference Period] (10) Irrigation Rate 1.42 Inches per Hour This valuemay be a default value or may be specified by user input; alternatively,catch cup measurement values 1314 may be used to generate this numberusing the following equation: ([Irrigation Rate in Inches per Hour] =[Average Catch Cup Reading for All Catch Cups 710 in Milliliters] *3.66) / ([Testing Run Time in minutes] * [Entrance Area to Catch Cup 710in Square inches]) Alternatively, the irrigation rate may be calculatedusing the following equation: ([Irrigation Rate in Inches per Hour] =[Average Catch Cup Reading for All Catch Cups 710 in Tenths of Inches])/ ([Testing Run Time in minutes] / [16 minutes] (11) Average of LowestQuartile of Catch Cup Values 13.63 Milliliters [Sum of all the moisturevalues within the lowest quartile of values 1312 of the catch cupmeasurement values 1314 (i.e., the quartile of the catch cups 710 thatreceived the smallest amount of moisture during the test run)] / [thenumber of catch cups 710 within the lowest quartile] (see Table 6) (12)Average of All Catch Cup Values 25.27 Milliliters [Sum of all the valuesreflecting moisture captured by the catch cups during the test run] /[the total number of catch cups 710 used in the test period] (See Table6) (13) Distribution Uniformity 54% Percent A default value may beapplied, may be specified by user or, alternatively, catch cupmeasurement values 1314 may be used to generate this number using thefollowing equation: [Average of the Lowest Quartile of Catch Cup Values]/ [Average of All Catch Cup Values] (14) Scheduling Multiplier 1.38Numeric This number is calculated using the following formula: 1 / (.4 +(.6 * [Distribution Uniformity])) (15) Available Water Value 0.14 Inches/ Inches Available Water may be ascertained, for example, with referenceto Table 7 based on soil type (16) Plant Available Water Depth 0.84Inches [Available Water Value (from Table 7)] * [Root Zone Depth 410](17) Replenishment Point Level 425 [Maximum Allowable Depletion 424](FIG. 4 of application 0.42 Inches [Available Water Depth 415] *([Maximum Allowable Depletion Value from Table 7 based, for example, onsoil type] / 100) (18) Irrigation Interval 2 Days Round Down to theNearest Whole Number of ([Replenishment point level] / [Average DailyETo]) (19) Water to Apply 0.38 Inches [Average daily ETo] * [IrrigationInterval] (20) Total Ideal Run Time per Day 16 Minutes / Day ([Water toApply] / [Irrigation Rate]) * 60 (21) Total Adjusted Run Time per Day 22Minutes / Days [Total Ideal Run Time per Day] * [Scheduling Multiplier](22) Maximum Run Time per Cycle 8 Minutes / Cycle ([Basic InfiltrationRate per the Soil Type take from, for example, Table 7] / [IrrigationRate]) * 60 (23) Cycles per Day 3 Cycle / Day Round up to the NearestWhole Number of ([Total Adjusted Run Time per Day] / [Maximum Run Timeper Cycle]) (24) Run Time per Cycle 7 Minutes / Cycle [Total AdjustedRun Time per Day] / [Maximum Run Time per Cycle]

Table 6 below provides one example of measurement values 1314 of catchcups 710 which may be used to carry out one or more steps of the method2000.

Table 6 is as follows:

TABLE 6 Cup No. Volume in Milliliters 1 50 2 42 3 41 4 40 5 40 6 36 7 358 35 9 34 10 34 11 34 12 34 13 32 14 30 15 29 16 29 17 28 18 28 19 27 2027 21 27 22 26 23 26 24 26 25 25 26 25 27 25 28 25 29 21 30 21 31 21 3221 33 20 34 19 35 19 36 18 37 16 38 16 39 16 40 15 41 14 42 14 43 12 4412 45 12 46 12 47 12 48 12 Average Cup Volume of Lowest Quartile of CupValues 13.63 Average Cup Volume of All Cups 25.27 DistributionUniformity (Average Cup Volume of Lowest Quartile of Cup Values /Average Cup Volume of All Cup Values) 0.54

Table 7 below illustrates example soil types and their associatedcharacteristics with typical or potential values. Values in Table 7 arealso employed in various locations in Table 5. These values may be usedto carry out one or more steps of the method 2000. The symbols,descriptions, and calculations identified in Table 7 are only exemplaryand are not limiting of the manner in which the method 2000 may beimplemented.

Table 7 is as follows:

TABLE 7 Soil Type Available Water Percentage of Root Zone Depth BasicInfiltration Rate Acre Inches Per Hour of Water That May Be Absorbed bythe Soil Maximum Allowable Depletion Percentage of Root Zone Depth WhenDivided by a 100 Clay 0.14 0.20 50 Clay Loam 0.16 0.25 50 Loam 0.12 0.3550 Sandy Loam 0.09 0.45 50 Sand 0.07 0.60 50

Continuing with FIG. 20 , the method 2000 may begin with step 2010 inwhich one or more measurement values 1314 representing a quantity ofwater captured by each catch cup 710 positioned within one of thewatering zones during a test watering period may be received by a catchcup component 1334.

In various embodiments, one or more measurement values 1314 may bereceived representing a quantity of water captured by each catch cup 710positioned within one of the one or more watering zones during a testwatering period, and the watering schedule may be automaticallyadjusted, without additional human intervention beyond inputting the oneor more measurement values 1314, based on the one or more measurementvalues 1314.

In step 2012, an average of the measurement values 1314 may becalculated by an average component 1332.

In step 2014, one or more measurement values 1314 falling within thelowest quartile of the values 1312 may be identified by a lowestquartile component 1366.

In step 2016, a lowest quartile average comprising an average of themeasurement values 1314 within the lowest quartile of the values 1312may be calculated by a lowest quartile average component 1364.

In step 2018, an estimated irrigation rate may be calculated based onthe lowest quartile average by an estimated irrigation rate component1336.

In step 2020, a first estimated in-soil water level 408 for the at leastone watering zone on the property at a first point in time may becalculated by an in-soil water level component 1362.

In step 2022, forecast evapotranspiration data 1316 for the at least onewatering zone for an intermediate period of time extending between thefirst point in time and a subsequent, second point in time may becalculated or received by a forecast evapotranspiration component 1338based on received forecast weather data 1320.

In step 2024, forecast precipitation data 1322 for the at least onewatering zone for the intermediate period of time may be received by aforecast weather component 1344.

In step 2026, a second estimated in-soil water level 408 at the secondpoint in time may be calculated based on the first estimated in-soilwater level 408, the forecast precipitation data 1322 and the forecastevapotranspiration data 1316 by an in-soil water level component 1362.

In step 2028, a scheduled watering time for the at least one wateringzone may be calculated without human intervention by a total scheduledwatering time component 1382 based at least in part on a ratio betweenan average of the lowest quartile of values 1312 and the average of themeasurement values 1314.

In step 2030, a watering schedule for the at least one watering zone maybe formulated without human intervention by a watering schedulecomponent 1390 based at least in part on the calculated scheduledwatering time.

In various embodiments, each of the steps of the method 2000 of FIG. 20may be performed entirely without human intervention with the exceptionof entering or specifying measurement values 1314 for the catch cups710. In various alternative embodiments, the method 2000 of FIG. 20 maybe performed entirely without human intervention when automatedsensor(s) 1238 are utilized to determine irrigation water to areaswithin a particular watering zone. The term “without human intervention”signifies that the steps are performed by a computing device without theneed for direction or input from a human being. Programming codeprepared by at least one human to perform the pertinent steps, as usedin this application, does not comprise human intervention.

Referring now to FIG. 21 , a flowchart is shown of a method 2100 forformulating a watering schedule based on a requested start time. Themethod 2100 may begin with step 2110 in which user input specifying therequested start time for one of the watering zones is received by arequested start time component 1374 and stored as start time data 1324.

In step 2112, a total desired watering time equal to a sum of desiredwatering times for each of the watering zones within a future temporalperiod may be calculated by a total desired watering time component1380.

In step 2114, permissible watering time periods within the futuretemporal period after the requested start time may be identified by afuture permissible watering time periods component 1340.

In step 2116, the permissible watering period nearest the requestedstart time employing the nearest identification component 1350 may beidentified. The nearest permissible watering period, in variousembodiments, may encompass the requested start time or may be thenearest permissible watering period after (or, alternatively, before)the requested start time.

In step 2117, the time that is (1) within the nearest permissiblewatering period and (2) after the requested start time is calculatedusing the time computation component 1352.

In step 2118, it may be determined whether the calculated time (1) afterthe requested start time and (2) within the nearest permissible wateringtime is less than the total desired watering time (or cumulativewatering or run time) by a start watering time adjustment component1376. If the calculated time is less than the total desired wateringtime, the method 2100 may proceed to step 2122. Alternatively, if thecalculated time is not less than the total desired watering time, themethod 2100 may proceed to step 2123.

In step 2120, the start time may be moved backward or forward in time,by a start watering time adjustment component 1376, relative to therequested start time. In various embodiments, the start time may bemoved forward in time so that watering may begin in a subsequentpermissible watering period, which may be greater in length than thetotal desired watering time. By way of example, if a permissiblewatering period in the morning and after the requested start time is notgreater than the total desired watering time, the start time may bemoved forward in time to begin watering during an evening permissiblewatering period. Alternatively, the start time may be moved backward intime relative to the requested start time to increase the watering timeduring a morning permissible watering period. In one such embodiment,after moving the start time backward in time within the morningpermissible watering time, the permissible watering time in the morningpermissible watering period and after the start time is greater than thetotal desired watering time.

In step 2122, a watering schedule may be formulated by the wateringschedule component 1390 based on the moved start time in accordance withthe moved start time.

In step 2123, a watering schedule may be formulated by the wateringschedule component 1390 based on the requested start time in accordancewith the requested start time.

In step 2124, a sprinkler controller may be operated by an operatingcomponent 1370 in accordance with the watering schedule.

Referring now to FIG. 22 , a flowchart is shown of a method 2200 forformulating a watering schedule based on one or more impermissibleperiods of time. The method 2200 may begin with step 2210, in which afirst estimated in-soil water level 408 for one of the watering zones onthe property at a first point in time may be calculated by an in-soilwater level component 1362.

In step 2212, an in-soil water capacity 420 of the at least one wateringzone may be calculated by an in-soil water capacity component 1360.

In step 2214, forecast evapotranspiration data 1316 for the at least onewatering zone may be calculated (based on received forecast weather data1320) by a forecast evapotranspiration component 1338 or received for anintermediate period of time extending between the first point in timeand a subsequent, second point in time, the second point in time beinglater than the first point in time, and the second point in timecomprising a beginning of an impermissible watering period for the atleast one watering zone.

In step 2216, forecast precipitation data 1322 for the at least onewatering zone for the intermediate period of time may be received by aforecast precipitation component 1342 for the intermediate period oftime.

In step 2218, a second estimated in-soil water level 408 for the atleast one watering zone at the second point in time may be calculated bythe in-soil water level component 1362 based on the forecastprecipitation data 1322 and the forecast evapotranspiration data 1316.

In step 2220, an estimated irrigation rate imparted by operation of thevalve associated with the at least one watering zone may be determinedby an estimated irrigation rate component 1336.

In step 2222, a difference between the second estimated in-soil waterlevel 408 and the in-soil water capacity 420 for the at least onewatering zone may be identified by a water level difference component1388.

In step 2224, a programming schedule may be set by a watering schedulecomponent 1390 for the valve associated with the at least one wateringzone such that the estimated in-soil water level 408 is elevated to theestimated in-soil water capacity 420 on or before the second point intime based on the estimated irrigation rate during one or morepermissible watering periods preceding the impermissible wateringperiod.

Referring now to FIG. 23 , a flowchart is shown of a method 2300 forformulating a watering schedule and transmitting a set of one or morerecommended changes. The method 2300 may begin with step 2310 in which afirst estimated in-soil water level 408 for one of the watering zones onthe property at a first point in time may be calculated by an in-soilwater level component 1362.

In step 2312, an estimated in-soil water capacity 420 of the at leastone watering zone may be calculated by an in-soil water capacitycomponent 1360.

In step 2314, forecast evapotranspiration data 1316 may be calculatedbased on received forecast weather data 1320 or received by a forecastevapotranspiration component 1338 for the at least one watering zone foran intermediate period of time extending between the first point in timeand a subsequent, second point in time, the second point in time beinglater than the first point in time, and the second point in timecomprising a beginning of an impermissible watering period for the atleast one watering zone.

In step 2316, forecast precipitation data 1322 for the at least onewatering zone for the intermediate period of time may be received by aforecast precipitation component 1342.

In step 2318, a second estimated in-soil water level 408 for the atleast one watering zone at the second point in time may be calculated bythe in-soil water level component 1362 based on the forecastprecipitation data 1322 and the forecast evapotranspiration data 1316.

In step 2320, current settings for the irrigation controller may beobtained by a current settings component 1394.

In step 2322, a set of one or more recommended changes to the wateringschedule component 1390 of the irrigation controller may be formulatedby a recommended changes component 1396.

In step 2324, an electronic notification of a set of one or morerecommended changes to the watering schedule may be transmitted by anotification component 1398.

Any methods disclosed herein comprise one or more steps or actions forperforming the described method. The method steps and/or actions may beinterchanged with one another. In other words, unless a specific orderof steps or actions is required for proper operation of the embodiment,the order and/or use of specific steps and/or actions may be modified,or various steps may be combined within the scope of the presentdisclosure.

Table 8 below illustrates a summary of some of the key words andconcepts discussed in the present disclosure, as well as some associatedexample values, units, and explanations. The items in Table 8 are onlyexemplary and are not intended to be limiting.

Table 8 is as follows:

TABLE 8 No. Name Example Value Units Explanation (1) Replenishment PointLevel 425 0.6 In-Soil Water Level 408 at Which All of the ReadilyAvailable Water 432 Has Been Depleted [Maximum Allowable Depletion 424(taken from, for example, Table 7)] * [Plant Available Water Depth] (2)Plant Available Water Depth [In-soil water capacity depth 412] -[Permanent Wilting Point Depth 428] (3) Estimated Time for the In-SoilWater Level 408 to Reach or Extend Below the Replenishment Point Level425 Considering, for 1.36 Days Days / Hours / Minutes ([EstimatedIn-Soil Water Level 408] - [Replenishment Point Level 425] +([Precipitation Received or Forecast] * [Application Efficiency])) /[Daily / Hourly / Minutely ETo] (Note: This equation applies when theestimated in-soil water level 408 is above or greater than thereplenishment point level 425. In various embodiments, if the estimatedin-soil water level 408 is at or below the replenishment point level425, watering should be Example, Evapotranspiration and Precipitationinitiated as soon as possible. Also, the portion of the equation“[Estimated In-Soil Water Level 408] - [Replenishment Point Level 425]”yields the condition -specific readily available water 422 within thepertinent soil 418 referenced in FIG. 4 .) (4) Replenishment Point LevelTime July 15 at 3:47 PM or Date / Time / Number of Day, Hours or Minutesfrom Here [Current Time] + [Estimated Time for the In-Soil Water Level408 to Reach or Extend Below the Replenishment Point Level 425Considering, for Example, Evapotranspiration and Precipitation] (5)Estimated In-Soil Water Level 408 0.24 Inches for Surface of Soil[Previous or Initial In-Soil Water Level 408] + ([Water Added byPrecipitation over the Period] + [Water Added by Irrigation in Inches] *[Application Efficiency]) - [Water Dissipated through Evapotranspirationin Inches] (6) Adjustment of Estimated In-Soil Water Level 408 -0.23Inches [Estimated In-Soil Water Level 408] + [ForecastEvapotranspiration - Historic Evapotranspiration] + ([HistoricPrecipitation - Forecast Precipitation] * [Application Efficiency]) (7)Total Open Valve Time 45 Time in Minutes Sum of [Run time for Each Zone](8) Total Desired Watering Time for All of The Watering Zones 45 Time inMinutes Sum of [Desired Watering Time for Each Zone] (Note: The desiredwatering time is the watering time that would be implemented if therewere no time restrictions or impermissible period wateringrestrictions.) (9) Estimated In-Soil Water Level Difference 1.2 Inches[In-soil water capacity 420] - [Estimated In-Soil Water Level 408 at theBeginning of an Impermissible Period] (10) Total Permissible WateringTime 140 minutes Days, Hours Minutes [Time in Temporal Period] - [TotalImpermissible Watering Time Within the Temporal Period]

Drought Management

Drought conditions can result in increased limitations on watering ofboth crops and landscape, including gardens, lawns, shrubbery, andtrees. Furthermore, simply constraining the irrigation to certainperiods of time (e.g., certain days of the week) does not always resultin a reduction in overall irrigation water consumption. For example,some users may irrigate more extensively during permissible wateringperiods, which may result in greater irrigation water consumption.Altering irrigation patterns in drought conditions can reduce overallwater consumption and, at the same time, optimize the water utilized.

Drought Management and Smart Watering

The drought settings may be used to adjust watering procedures for smartwatering (in which an algorithm specifies start times, wateringfrequency and watering duration (sometimes referred to as “run time”)for each zone based on, for example, historical weather data 1308 and/orforecast weather data 1320) or for custom watering procedures (in whicha user specifies start times and zone watering duration for each zone).Methods and apparatuses for adjusting for drought conditions inconnection with smart watering will be discussed in connection withFIGS. 24-35 , while methods and apparatuses for adjusting in connectionwith custom watering will be discussed in connection with FIGS. 36A-39 .

FIG. 24 illustrates a drought information screen 2400 comprising a map2450 illustrating different categories 2440 of drought conditions. Asillustrated, drought conditions may be categorized, for example, into anumber of different categories 2440, such as none (no drought), D0(abnormally dry), D1 (moderate drought), D2 (severe drought), D3(extreme drought), D4 (exceptional drought) or, no data (no data isavailable for a specified area). As illustrated in the map 2450 of FIG.24 , drought conditions may vary substantially within a specified area,such as within a state of the United States of America. The differentdrought categories 2440 illustrated in FIG. 24 merely serve as anexample. By way of example only, a drought may be categorized into 10different classifications, each with varying degrees of severity.

FIG. 25 illustrates one embodiment of a drought settings user interface2500 of an application (e.g., an application running on a desktopcomputer, laptop or a mobile device or within a web browser). Thedrought settings user interface 2500 notifies the user that the area inwhich the pertinent irrigation system is located is in a drought. Thelocation of the pertinent irrigation system or a zone within theirrigation system may be determined in various ways. For example, a usermay input an address, city and state, or ZIP Code of the pertinentproperty during the setup process for the associated irrigationcontroller. Alternatively, the associated irrigation controller for theirrigation system may include a GPS device for determining the locationof the irrigation controller. As an additional alternative, the user maybe prompted to input GPS coordinates from a phone or may provide asoftware application or module for providing the GPS coordinates viaphone to a system in communication with the irrigation controller forone or more of the zones within a property serviced by the irrigationcontroller.

The illustrative user interface 2500 indicates that the pertinentproperty is experiencing drought category D2 and requests the user toeither change to a D2 drought setting (employing a change to D2 control2510) or to ignore the prompt (using a ignore control 2512). In responseto selecting the change to D2 control 2510, irrigation controllersettings for a selected zone or all of the zones may be transitioned tosettings adapted to drought category D2 depending on the embodiment ofthe invention or specified user settings. Of course, similar screenscould apply to the other drought categories (e.g., drought category D0or drought category D4). Activating the ignore control 2512, wouldresult in no changes to the irrigation controller settings.

As used herein, the term “control” refers to a portion of a userinterface used to alter a setting or trigger an action. The controlcould comprise, for example, a graphical icon or a link on ascreen-based user interface. The term “control” may also refer to aphysical mechanism for altering the settings or triggering an action ofa device, such as a physical button, dial or toggle switch.

FIG. 26 illustrates one embodiment of a drought notification userinterface 2600 of a software application. This user interface 2600 alsoprovides notice to the user that the pertinent property is experiencinga drought. The illustrated user interface 2600 includes a check droughtconditions control 2610, an edit drought settings control 2612, and adismiss control 2614. The check drought conditions control 2610 may beused to identify a pertinent drought category 2440 either manually or inan automated way. For example, activating the check drought conditionscontrol 2610, may trigger, for example, the presentation of the droughtinformation screen 2900 of FIG. 29 or the drought information screen2400 of FIG. 24 or could present a screen showing the applicable droughtcategory for the location of the pertinent property. The edit droughtsettings control 2612 could trigger the presentation of a user interfacefor editing the drought settings for a watering zone or for an entireirrigation system, such as the user interface 2700 illustrated in FIG.27 . The dismiss control 2614 dismisses the presented informationwithout taking further action.

FIG. 27 is a drought settings user interface 2700 of an application thatenables a user to select a drought category 2440 for a particularproperty serviced by an irrigation controller or a set of irrigationcontrollers (i.e., a set of watering zones) or for a watering zone. Theuser may manually obtain the information, such as using the informationscreen 2400 of FIG. 24 or the information screen 2900 of FIG. 29 , andthen select a corresponding or desired drought category control2760-2765. Alternatively, a location of the watering zone may bedetermined in an automated manner. In such a situation, the estimatedgeographic location of a watering zone or a property to be watered(comprising one or more watering zones) may be determined, using, forexample, as indicated above, GPS coordinates of an irrigation controlleror of a phone positioned within or near the watering zone or property orvia user input specifying the location of the zone or property (e.g., byspecifying a ZIP Code, address, or city and state, potentially duringthe irrigation controller set up process). As noted, the “estimatedgeographic location” may be an approximate location. For example, a usermay be situated on or proximate the property on which the zone islocated and simultaneously obtain GPS coordinates for one or more zonesthrough an app running on the user’s phone. Alternatively, the user mayobtain different GPS coordinates for each zone by positioning a phone ora tablet in each zone and obtaining GPS data from an app on the user’sphone or tablet. Thereafter, drought data related to that particularlocation may be obtained through an electronic connection to a remoteserver (such as the server(s) 1200 b or weather data provider(s) 1252illustrated in FIG. 12A or another server). This automated operation maybe triggered in response to activation of a control on the userinterface 2600 illustrated in FIG. 26 , such as by tapping on the checkdrought conditions control 2610 illustrated on the user interface 2600.Thereafter, a drought category indicator 2735 may be presented on theuser interface 2700 adjacent to a control 2763 representing a particulardrought category 2440. As illustrated in FIG. 27 , the drought categoryindicator 2735 may comprise an outline around the control 2763 or couldcomprise another visual indicator, such as a pointer or triangle. Theuser may select the control 2763 associated with the indicated droughtcategory 2440 or a control 2760, 2761, 2762, 2764, 2765 representinganother drought category 2440. In an alternative embodiment, the droughtcategory is automatically selected without requesting validation orapproval from a user once a user has opted into adjustment of thepertinent watering schedule(s) based on drought data.

The check drought level control 2785, when activated, may bring up, forexample, the drought information screen 2400 of FIG. 24 or the droughtinformation screen 2900 of FIG. 29 . Alternatively, the check droughtlevel control 2785 may also be used to connect to a server and obtain,as explained above, updated drought level data pertaining to a specificgeographic location, e.g., for the zone or property of interest.

FIG. 28 illustrates one embodiment of an additional view of a droughtsettings user interface 2700 of FIG. 27 with the advanced zone settingscontrol 2840 activated such that a drought factor user interface 2860 isdisplayed. The illustrated drought factor user interface 2860 includes aslide bar control for selecting a drought factor between and including1.0 and 0.5, as illustrated in FIG. 28 . The drought factor userinterface 2860 could be configured in alternative ways, such as a textbox or drop-down menu for entering a desired drought factor. A droughtfactor may be used in calculating a modified irrigation schedule and maycorrespond to a particular drought category 2440 or could be manuallyestablished utilizing the drought factor user interface 2860. Thedrought factor will be subsequently discussed in additional detail.

FIG. 29 illustrates one embodiment of a drought information screen 2900.The information screen 2900 may comprise a map 2950 indicating differentdrought categories 2440 within a region along with a listing of thepossible drought categories 2440 embodied as a key for the map 2950. Ofcourse, as noted above, alternative drought categories are possible,such as, by way of example only, ten different drought categories.

FIG. 30 is a zone application user interface 3000 of the application,which allows the user to apply the selected drought category 2440 to allzones (employing the apply to all zones control 3070) for a particularsystem or to merely a selected zone (employing the only selected zonecontrol 3071). The user interface 3000 illustrated in FIG. 30 isoptional and merely illustrative of potential interfaces for specifyinghow the drought settings are applied. Alternatively, for example, thesystem could be configured to apply the drought settings to only aselected zone, a set of zones, or to all the zones by default or basedon user-specified settings.

As illustrated in FIG. 31 , in the zone settings user interface 3100, auser may specify settings for one or more zones, such as soil type,plant type, sprinkler type, sun/shade exposure, effective rainfall(which may be used to indicate whether rainfall to a particular zone isobstructed, such as by a tree or portion of a building), slope,sprinkler count, catch cups, and drought settings.

The settings implemented by the user interfaces 2500, 2600, 2700, 3000,3100 are illustrated in FIGS. 25-31 may be activated and altered byusers using, for example, one or more mouse clicks, finger taps,hotkeys, touchscreen gestures, voice recognition commands, or gesturesprovided above the screen. It should be noted that the user interfaces2500, 2600, 2700, 3000, 3100 serve as non-limiting examples of thesetypes of user interfaces.

FIGS. 32A-32B illustrate an alternative embodiment of an irrigationcontroller 3200. As noted previously, the irrigation controller 3200 maybe implemented in whole or in part on one or more local devices 1400 a,servers 1500 b and/or end-user devices 1600 c (e.g., a tablet or phone).Descriptions and variations of the previously described components willnot be reiterated here, but are expressly incorporated by thisreference. As indicated in FIGS. 32A-32B, the data 3202 of theirrigation controller 3200 further includes drought data 3203, and theirrigation controller 3200 comprises a drought determination component3204, a drought factor component 3205, and a drought adjustmentcomponent 3206. The drought data 3203 may include, for example, adrought category 2440 for a specific geographic location of one or moreof the zones for a particular property, as indicated above, and may alsoinclude geographic data for one or more of the zones.

The drought determination component 3204 may determine droughtconditions for a particular zone or set of zones. For example, thisdetermination may be made in response to user input specifying a droughtcategory for a particular zone or set of zones or, alternatively, may bemade using position data (e.g., GPS data) for determining an approximategeographic location of a zone or set of zones and drought data 3203corresponding to that approximate geographic location. Data indicating adrought category for a particular zone or set of zones may be storedwith the drought data 3203. The drought determination component 3204 maycomprise, for example, a combination of hardware and/or software.

The drought factor component 3205 may determine a set of one or moredrought factors associated with the determined drought category. Thedrought factors may be utilized to determine that adjustments should bemade, for example, to watering frequency, watering duration, and/or alandscape evapotranspiration rate. Adjustments to the landscapeevapotranspiration rate impact watering frequency. Each drought factormay be calculated or may be retrieved from a data structure thatassociates each drought category with one or more drought factors. Thedrought factor component 3205 may comprise a combination of hardwareand/or software.

A separate drought factor may be used for adjustment, for example, ofeach of watering frequency, watering duration, and/or the landscapeevapotranspiration rate. Other drought factors and types of droughtfactors may be utilized. Examples of drought factors are illustrated inconnection with Tables 9 and 10, which are discussed hereafter. Asnoted, one or more drought factors may be associated with each droughtcategory.

The drought adjustment component 3206 may be utilized to adjust wateringtimes and/or watering frequency based on one or more drought factors.The drought adjustment component 3206 may operate in various ways. Inone embodiment, for example, an adjusted landscape ET(evapotranspiration) rate may be calculated as follows:

$\begin{array}{l}{\text{Adjusted Landscape ET Rate} = \lbrack \text{Reference ET}_{\text{O}} \rbrack*} \\{\lbrack {\text{Landscape Coefficient}( \text{K}_{\text{L}} )} \rbrack*\lbrack {\text{Drought Factor}( \text{K}_{\text{DR}} )} \rbrack}\end{array}$

The drought adjustment component 3206 may comprise software or acombination of software and hardware (e.g., a processor and memory)located on various discrete devices or on a single device. The droughtadjustment component 3206 may calculate the adjusted landscapeevapotranspiration rate utilizing, for example, Equation 1. The droughtadjustment component 3206 may interact with the watering schedulecomponent 1390 to change the watering schedule for one or more wateringzones in accordance with the adjusted landscape evapotranspiration rate,i.e., utilizing the adjusted landscape evapotranspiration rate in placeof the landscape evapotranspiration rate in determining wateringduration, watering frequency, and/or start times in connection withsmart watering.

As discussed in further detail below, the drought adjustment component3206 may also be utilized to adjust watering frequency and wateringduration in connection with either smart or custom watering.

The following table, Table 9, illustrates potential drought factors foreach drought category 2440. It should be noted that the followingdrought factors are merely illustrative, and other drought factors(e.g., 0.66) may be utilized within the scope of the disclosed subjectmatter.

TABLE 9 Drought Category Drought Factor (K_(DR)) None (no drought) 1.00D0 (abnormally dry) 0.95 D1 (moderate drought) 0.90 D2 (severe drought)0.85 D3 (extreme drought) 0.80 D4 (exceptional drought) 0.75 No Data1.00

For example, if the drought factor is 0.8, the landscape ET will bereduced per Equation 1 (i.e., reduced by 20%), resulting in an increasedperiod of time between watering intervals, because the system, bydesign, decreases the calculated landscape evapotranspiration rate,i.e., the determined landscape ET is reduced. In an alternativeembodiment, the user may manually establish the drought factor withoutreference to a particular drought category 2440. By way of example only,the user may set the drought factor between and including from 1.0 to0.5 in increments of 0.05 using the drought factor user interface 2860of FIG. 28 . In an alternative embodiment, the user may manually set thedrought factor to any value between a specified range (e.g., between andincluding 1.0 and 0.5) via, for example, a text box interface. It shouldbe noted that the drought factor does not alter the landscape ET if thedrought factor is set to 1.0. The irrigation controller 3200 may beutilized to perform one or more of the methods described in connectionwith FIGS. 33-35 .

In alternative embodiments, an adjusted evapotranspiration rate may beutilized for irrigation systems that do not incorporate a landscapecoefficient which is referenced in Equation 1. Therefore, in suchsystems, the evapotranspiration rate (an evapotranspiration rateindependent of landscape conditions) may be altered using, for example,a drought factor as indicated above.

It should be noted that a user may specify smart watering for certainzones and custom watering for other zones within the same system.Therefore, when a user selects custom watering for a particular zone,the drought adjustment component 3206 may perform different functionsfor that zone or set of zones. For example, when custom watering isselected for a particular zone, a drought factor may be multiplied by awatering duration for that zone to calculate an adjusted wateringduration. If the drought determination component determines that droughtcategory D3 (extreme drought) applies to the watering zone at issue,this drought category may correspond to a drought factor of 0.80, asindicated in Table 9. Therefore, by way of example, if the userspecifies that a particular zone runs for 30 minutes three times a week,and the drought factor is 0.80, the adjusted watering duration may be 24(i.e., 30 × 0.8 = 24) minutes three times a week. Alternatively, theinterval of time between watering may be augmented, such as (1) bydividing the interval of time between watering by the drought factor (anumber less than one and greater than zero) or (2) by increasing thenumber of intervening non-watering days between days on which wateringoccurs.

FIG. 33 is a flow diagram illustrating one method 3300 for adjusting anirrigation schedule based on determined drought conditions, such as adetermined drought category. In step 3310, an estimated geographiclocation of a watering zone is determined. As noted previously, thegeographic location may be determined, for example, using an end-userdevice 1200 c comprising a mobile phone or GPS sensor disposed within alocal device 1200 a or through the specification of an address or ZIPCode.

In step 3312, a drought category 2440 assigned to the estimatedgeographic location is determined. In one embodiment, the droughtcategory 2440 may be determined based on user input, i.e., the user mayreview a drought map and identify the user’s location on the map and theassociated drought category. In an alternative embodiment, a droughtcategory 2440 is retrieved, for example, from a remote server based on adetermined or estimated geographic location, such as GPS coordinates ofa phone or a local device 1200 a, or manually specified GPS coordinatesor ZIP Code.

In step 3314, a user interface identifying the determined droughtcategory 2440 may be presented. For example, a drought settings userinterface 2700 may present a drought category indicator 2735. Theindicator 2735 could be embodied in different ways, as explained above.

In step 3316, user input altering or confirming a drought category 2440for the watering zone is received. This user input may be provided, forexample, through the drought settings user interface 2700 via one ormore mouse clicks, finger taps, hotkeys, touchscreen gestures, voicerecognition commands, or in-air gestures provided above the screen toone of the drought category controls 2760-2765.

In step 3318, an adjusted landscape evapotranspiration rate for thewatering zone is calculated based on the determined drought category2440. The adjusted landscape evapotranspiration rate may be calculated,for example, using the drought factor associated with the pertinentdrought category using Equation 1.

In step 3320, a watering schedule for the watering zone is adjusted inaccordance with the adjusted landscape evapotranspiration rate. As notedpreviously, the watering schedule may be adjusted by reducing thecalculated landscape evapotranspiration rate, which, in turn, reducesthe frequency of watering intervals (i.e., because it takes longer toreach the determined replenishment point level 425).

In step 3322, the zone is watered in accordance with the adjustedwatering schedule.

FIGS. 34-35 describe alternative methods 3400, 3500 for adjusting awatering schedule based on determined drought conditions, such as adetermined drought category. With respect to the method 3400 of FIG. 34, in step 3411, a watering schedule is formulated based on at least alandscape evapotranspiration rate as delineated, for example, inconnection with Table 5 and FIG. 17 . The watering schedule may beformulated using a number of different methods, such as partially orcompletely filling up a watering zone when a particular water level(e.g., the replenishment point level 425) is reached within the wateringzone. In step 3414, the drought category is determined using, forexample, (1) user input specifying a drought category 2440 for thewatering zone or (2) based on drought data and an estimated geographiclocation of the watering zone, as explained, for example, in connectionwith steps 3310 and 3312 of FIG. 33 . In step 3416, a drought factorassociated with the drought category 2440 is determined, using, forexample, an electronic data structure associating a drought factor witha drought category 2440 (e.g., as illustrated in Table 9). In step 3418,an adjusted landscape evapotranspiration rate for the watering zone iscalculated based on the determined drought factor, as explained, forexample, in connection with Equation 1. In steps 3320 and 3322, asdescribed above, a watering schedule is adjusted and the zone is wateredin accordance with the adjusted schedule.

With respect to the method 3500 of FIG. 35 , in step 3516, user inputspecifying a drought factor for a watering zone is received. Forexample, the user input may be provided via a text field or via adrop-down menu of selectable drought factors or using a drought factoruser interface 2860, as discussed in connection with FIG. 28 . In step3518, an adjusted landscape evapotranspiration rate for the wateringzone is calculated based on the specified drought factor, utilizing, forexample, Equation 1. In steps 3320 and 3322, as described above, awatering schedule is adjusted and the zone is watered in accordance withthe adjusted schedule.

The foregoing methods 3300, 3400, 3500 could be applied not just to onezone but a set of zones, such as zones for a particular property orirrigation controller or for a set of irrigation controllers.

In various embodiments, the drought factor may be utilized to reducewatering duration or watering frequency for a zone, as explained belowin connection with FIGS. 36A-B. However, while these alternate methodsmay be utilized, the method described above in connection with Equation1 reduces water consumption while at the same time producing excellentoutcomes given the watering constraints.

As noted above, multiple drought factors may be associated with a singledrought category in connection with smart watering. Therefore, a singledrought category could result in an adjusted landscapeevapotranspiration rate (which could impact watering frequency, starttimes, and/or watering duration) and/or direct modification of thewatering duration or watering frequency generated by a smart wateringalgorithm. For example, a watering duration calculated by a smartwatering algorithm may be multiplied by a drought factor less than 1.0and greater than zero to generate an adjusted watering duration for awatering zone during drought conditions, as discussed below inconnection with custom watering in relation to FIG. 36A. Also(additionally or alternatively), a drought factor could be used todirectly increase the number of intervening non-watering days (oranother time unit) between days (or times) on which watering isscheduled to occur (in accordance with a watering schedule formulated bya smart watering algorithm), as discussed in relation to custom wateringin connection with FIG. 36B.

Drought Management and Custom Watering

As noted previously, smart watering involves automated adjustments to orformulation of watering start times, watering frequency and/or thewatering duration. In contrast, when custom watering is implemented, thewatering frequency (e.g., every three days or every Monday, Wednesday,and Friday), start times and watering durations (e.g., 30 minutes) areestablished manually by a user. In one implementation, droughtmanagement for custom watering will also involve use of one or moredrought factors, which were previously referenced. As noted above, thefunctional blocks of the irrigation controller 3200 illustrated in FIGS.32A-B may also be utilized in connection with drought management forcustom watering. For example, the drought data 3203 may be utilized bythe drought determination component 3204 to determine a drought categoryfor a watering zone or set of watering zones. The drought factorcomponent 3205 may be utilized to determine a set of one or more droughtfactors associated with a determined drought category. The droughtadjustment component 3206 may calculate the adjusted watering durationsand/or adjusted watering frequency based on one or more drought factors.The watering schedule component 1390 may alter the watering schedule inaccordance with, for example, the adjusted watering frequency and theadjusted watering duration.

It should also be noted that the user interfaces illustrated forselecting a drought factor and drought category (FIGS. 24-31 ) for smartwatering may also be utilized in connection with drought adjustment forcustom watering. Therefore, as explained in connection with smartwatering, the user could receive a notification of drought conditionsand be prompted to make alterations, by either establishing the droughtfactor directly, for example, in connection with the drought factor userinterface 2860 illustrated in FIG. 28 or by selecting a drought category2440, for example, utilizing one of the drought category controls2760-2765 illustrated in FIG. 27 , which may be correlated to a droughtfactor, as explained in connection with Table 9. In alternativeembodiments in connection with both smart and custom watering, the usercould select an option that allows automatic detection of a droughtcategory and establishes, without further user action, a drought factorfor one or more of the watering zones. Also, automatic detection of adrought category may take place, in certain embodiments, without anyuser modification of the options as this could be the default setting oreven the only approach implemented by an irrigation controller inconnection with both smart and custom watering.

FIG. 36A is a table 3600 that illustrates various methods of adjusting awatering schedule based on a determined drought category for a zone whencustom watering is implemented. As noted previously, when customwatering is implemented, a user specifies start times, wateringfrequency, and/or watering duration for each watering zone or set ofwatering zones. In the embodiment illustrated in the table 3600 of FIG.36A, a drought factor is utilized. In this situation, however, thedrought factor is not utilized to calculate an adjusted landscapeevapotranspiration rate. Instead, the drought factor is utilized toreduce the watering duration for each watering zone. Thus, theillustrated table 3600 includes a watering zone column 3610, a wateringfrequency and duration before drought adjustment column 3612, a droughtfactor column 3614, and a watering frequency and duration after droughtadjustment column 3616. As illustrated in the table 3600, the wateringduration after drought adjustment is multiplied by the drought factor.Because the drought factor is one or less than one, the drought factoreither reduces the watering duration after drought adjustment when thedrought factor is less than 1.0 or leaves it the same when the droughtfactor is equal to 1.0. Accordingly, the water utilized is reducedemploying the drought factor when the drought factor is less than one.This is significant because by merely adjusting the drought factor forall of the watering zones, one of the watering zones, or each of thewatering zones, the watering is reduced without manually reconfiguringeach station. When the drought conditions subside, the drought factormay be adjusted to one, without requiring the user to manually adjustthe watering times for each station.

In connection with custom watering, the pertinent data may be stored inthe drought data 3203 and pertinent adjustments will be made by thedrought adjustment component 3206, such as those illustrated in thetable 3600 illustrated in FIG. 36A.

FIG. 36B is a table 3650 illustrating additional methods for adjusting awatering schedule for drought conditions when custom watering isimplemented. In this embodiment, one or more drought factors areutilized, as illustrated in Table 10, which is provided below. Thecolumns in the table 3650 identify a watering zone column 3610, adrought category column 3611, watering frequency and duration beforedrought adjustment column 3662, drought factors column 3664, andwatering frequency and duration after drought adjustment column 3666.The method illustrated in the table 3650 involves decreasing thefrequency of watering by increasing the interval of time betweenwatering and decreasing watering duration. In alternative embodiments,only the frequency of watering may be adjusted or, as illustrated inconnection with table 3600, only the watering duration may be modified.For example, as illustrated in the table 3650 of FIG. 36B, a firstdrought factor in the drought factors column 3664 is a positive numberless than or equal to 1.0 and a second drought factor in the droughtfactors column 3664 could be a positive integer, such as 1 or 2. Thefirst drought factor is illustrated and discussed in connection with thetable 3600 of FIG. 36A and is utilized to reduce the watering duration.This discussion will focus on the second drought factor in the droughtfactors column 3364, as this drought factor has not been explainedpreviously. If the second drought factor is 1, the number of interveningnon-watering days is increased by 1, as illustrated in the third row ofthe table 3650, which pertains to watering zone 1. Therefore, in thissituation, if the user manually specified watering every two days, thesystem would transition to watering every three days, as illustrated inthe third row of the table 3650. As noted previously and as illustratedin the table 3650, the first drought factor may be utilized to alter thewatering duration for the watering zone at issue as is the case in theexample provided in the third row of the table 3650.

TABLE 10 Drought Category First Drought Factor (for decreasing wateringduration) Second Drought Factor (for increasing the number ofintervening non-watering days relative to the user-specified wateringfrequency) None (no drought) 1.00 0 D0 (abnormally dry) 0.95 0 D1(moderate drought) 0.90 0 D2 (severe drought) 0.85 1 D3 (extremedrought) 0.80 1 D4 (exceptional drought) 0.75 2 No Data 1.00 0

Decreasing watering frequency could also take other forms, asillustrated in the sixth row of the table 3650. In this row, the userspecified that zone 4 waters for 24 minutes on Monday, Wednesday andFriday. Therefore, the intervening period between Monday and Wednesdayand between Wednesday and Friday is one day (1 intervening non-wateringday), while the intervening period between Friday and Monday is two days(2 intervening non-watering days). If the second drought factor is 1,then the number of intervening non-watering days is increased by one,yielding a cycle of 2, 2, and 3 intervening non-watering days betweenuser-specified watering days (i.e., watering on Monday (followed by 2intervening non-watering days), the next Thursday (followed by 2intervening non-watering days), the next Sunday (followed by 3intervening non-watering days), the next Thursday (followed by 2intervening non-watering days), the next Sunday (followed by 2intervening non-watering days), the next Wednesday (followed by 3intervening non-watering days), and the next Sunday (followed by 2intervening non-watering days), etc.).

Of course, other variations are possible. For example, the minimum ormaximum number of intervening non-watering days of a user-specifiedwatering schedule for a zone may be considered as a base value andincreased when drought management is implemented. Following oneembodiment of such an algorithm, if the user-specified watering everyMonday, Wednesday, and Friday, the minimum intervening non-watering dayis one. Therefore, if the second drought factor of 1 is utilized, thesystem transitions the watering schedule to watering once every threedays (with 2 intervening non-watering days between every watering day).

The irrigation controller 3200 may be utilized to perform one or more ofthe methods described in connection with FIGS. 37-39 .

FIG. 37 is a flow diagram illustrating one method 3700 for adjusting anirrigation schedule based on a drought factor when custom watering hasbeen implemented. In step 3710, an estimated geographic location isdetermined for example, using a mobile device or GPS sensor disposedwithin an irrigation controller (e.g., a local device 1200 a) or using aspecified address or ZIP Code.

In step 3712, a drought category 2440 assigned to the estimatedgeographic location is determined. In one embodiment, the droughtcategory 2440 may be determined manually, i.e., the user may review adrought map and identify the user’s location on the map. In analternative embodiment, a drought category 2440 is retrieved, forexample, from a remote server based on a determined or estimatedgeographic location, such as GPS coordinates of a phone or irrigationcontroller, or manually specified GPS coordinates (e.g., specifiedduring the setup process for an irrigation controller) or ZIP Code.

In step 3714, a user interface identifying the determined droughtcategory 2440 may be presented. For example, a drought settings userinterface 2700 may present a drought category indicator 2735. Theindicator 2735 could be embodied in different ways, as explained above.

In step 3716, user input altering or confirming a drought category 2440for the watering zone is received. This user input may be provided, forexample, through the drought settings user interface 2700 via one ormore mouse clicks, finger taps, hotkeys, touchscreen gestures, voicerecognition commands, or in-air gestures provided above the screen toone of the drought category controls 2760-2765.

In step 3718, a set of one or more drought factors associated with thedetermined drought category is determined, using, for example, a datastructure incorporating data illustrated in Table 9 or Table 10.

In step 3720, a watering schedule for the watering zone is adjusted inaccordance with the determined set of one or more drought factors (e.g.,based on adjusted watering durations and/or adjusted wateringfrequencies for one or more watering zones calculated based on the setof one or more drought factors). As noted previously and as illustratedin connection with FIGS. 36A-B, one or more watering durations for eachwatering zone may be multiplied by a drought factor. When the droughtfactor is less than one, this results in a reduction of the wateringduration. In addition or alternatively, another type of drought factormay be utilized to decrease watering frequency, as explained inconnection with FIG. 36B.

In step 3722, the zone is watered in accordance with the adjustedwatering schedule.

FIGS. 38-39 describe alternative methods 3800, 3900 for adjusting awatering schedule when custom watering is utilized. With respect to themethod 3800 of FIG. 38 , in step 3813, user input specifying a wateringfrequency and watering duration for a watering zone is received at auser interface. One example of such a user interface is illustrated inconnection with FIG. 1 . In the user interface of FIG. 1 , the “HowOften” mode may be utilized to specify watering frequency, while the“Run Time” mode may be utilized to specify watering duration. Of course,a start time may also be specified by a user. FIG. 2 also illustrates auser interface through which a start time, watering frequency, and awatering duration for a particular zone or set of zones may be specifiedby a user. Also, user input may specify the use of the default valuesfor watering frequency, watering duration, and start time by opting notto alter the default values.

In step 3815, a watering schedule may be formulated based on user inputspecifying watering frequency, watering duration and/or a start time fora zone. This formulation step 3815 involves the conversion of the userinput into a watering schedule that may be stored and utilized by thepertinent irrigation controller.

In step 3816, a drought category for a watering zone may be determined.This determination may be made based on user input specifying a droughtcategory or may be made, for example, based on drought data 3203 and anestimated geographic location of the watering zone.

In step 3818, one or more drought factors associated with the determineddrought category may be determined using a data structure incorporating,for example, the information included in Table 9 or Table 10.

In step 3819, at least one of an adjusted watering frequency and anadjusted watering duration for the watering zone is calculated using oneor more drought factors. This calculation may involve, for example, thecalculations illustrated in connection with FIGS. 36A-B.

In step 3820, at least one of the adjusted watering frequency and theadjusted watering duration may be utilized to adjust the wateringschedule. This adjustment may be performed by the watering schedulecomponent 1390.

In step 3822, the watering zone may be watered in accordance with theadjusted watering schedule.

With respect to the method 3900 of FIG. 39 , in step 3918, user inputspecifying a drought factor for a watering zone is received. Forexample, the user input may be provided via a text field, a drop-downmenu or a slide bar control of selectable drought factors. In step 3920,the watering schedule for the watering zone is adjusted in accordancewith the specified drought factor, as illustrated, for example, inconnection with FIGS. 36A-B. In step 3722, as described above, the zoneis watered in accordance with the adjusted schedule.

The foregoing methods 3700, 3800, 3900 could be applied not just to onezone but a set of zones, such as zones for a particular property, allzones controlled by a particular irrigation controller or all zonescontrolled by a set of irrigation controllers. In addition, certainsteps illustrated in the methods 3700, 3800, 3900 may be omitted or theorder of those steps may be altered.

In various embodiments, a user interface may be provided that enablesselection of either drought management for custom watering based ondecreasing watering frequency and/or decreasing watering duration on aper-zone basis. Therefore, the user may select decreasing wateringfrequency on a first zone for a system and decreasing watering durationon a different zone for the same system. The foregoing is also true forsmart watering. Therefore, a smart watering zone may enable adjustmentsto the landscape evapotranspiration rate, the watering frequency, and/orthe watering duration, as outlined in the examples provided above, inaccordance with the system capabilities specified by a manufacturer ofan irrigation controller and user-specified options. A custom wateringzone may enable adjustments to the watering frequency and the wateringduration, again as outlined in the examples provided above. A singlesystem may involve user-selectable options that allow smart watering orcustom watering on a per-zone basis in addition to specifying one of thevarious methods of drought management (e.g., adjusted landscapeevapotranspiration rate, adjusted watering frequency, and adjustedwatering duration) on a per-zone basis.

It should be noted that the drought factors shown in Tables 9 and 10 aremerely illustrative. It should additionally be noted that, in variousembodiments, different drought factors may be utilized, for example, forcalculating each of the adjusted landscape evapotranspiration rate, theadjusted watering frequency, and the adjusted watering duration.

One advantage of the foregoing systems and methods is that when droughtconditions have subsided, the user may rapidly return to the priorwatering settings (whether to prior smart watering settings or to priormanual watering settings) by, for example, setting the drought factor to1.0 or the drought category to “none”, as opposed to reconfiguring anumber of different settings for each zone.

In various embodiments, notifications will be provided to usersregarding any potential changes related to drought management. Thosenotifications could include, for example, a visual or audionotification. In the case of a visual notification, the modifiedwatering schedule might be presented for approval or rejection by theuser. Such a notification is illustrated, for example, in connectionwith FIG. 25 which allows, using the ignore control 2512, a user toreject the proposed drought settings.

It is understood that any specific order or hierarchy of steps in anydisclosed process is an example of a sample approach. Based upon designpreferences, it is understood that the specific order or hierarchy ofsteps in the processes may be rearranged while remaining within thescope of the present disclosure. The accompanying method claims presentelements of the various steps in a sample order and are not meant to belimited to the specific order or hierarchy presented. In addition, withrespect to the methods disclosed, alternative variations of thedisclosed subject matter may involve not only rearranging certain stepsbut omitting certain steps within the scope of the disclosed subjectmatter. In addition, the omission of one or more blocks or elementswithin the functional or schematic block diagrams and the rearranging ofthe order of one or more blocks or elements is also within the scope ofthe disclosed subject matter.

1. An irrigation controller for adjusting a watering schedule for awatering zone based on determined drought conditions, the irrigationcontroller being configurable to control irrigation of the watering zonein accordance with the watering schedule, the irrigation controllercomprising: a set of one or more processors; a watering schedulecomponent for formulating a watering schedule for a watering zone usingat least one processor of the set of one or more processors based on atleast a landscape evapotranspiration rate for the watering zone; adrought determination component for determining a drought category forthe watering zone; and a drought adjustment component for calculating anadjusted landscape evapotranspiration rate for the watering zone basedon the determined drought category using at least one processor of theset of one or more processors, wherein the watering schedule componentis further configured to adjust the watering schedule for the wateringzone in accordance with the adjusted landscape evapotranspiration rateusing at least one processor of the set of one or more processors. 2.The irrigation controller of claim 1, wherein the drought adjustmentcomponent is configured to calculate the adjusted landscapeevapotranspiration rate by multiplying a drought factor associated withthe determined drought category by the landscape evapotranspirationrate.
 3. The irrigation controller of claim 2, wherein the droughtfactor is less than 1.0.
 4. The irrigation controller of claim 2,further comprising a second drought factor associated with thedetermined drought category for calculating an adjusted wateringduration.
 5. The irrigation controller of claim 1, wherein the droughtadjustment component determines the drought category based on user inputspecifying the drought category.
 6. The irrigation controller of claim1, wherein the drought adjustment component determines the droughtcategory based on drought data and an estimated geographic location ofthe watering zone.
 7. The irrigation controller of claim 1, wherein theirrigation controller comprises at least two of a server, a localdevice, and a mobile end-user device.
 8. A method for adjusting awatering schedule stored on an irrigation controller based on determineddrought conditions, the irrigation controller being configurable tocontrol irrigation of a watering zone in accordance with the wateringschedule, the method comprising: formulating, using at least oneprocessor of a set of one or more processors, a watering schedule for awatering zone based on at least a landscape evapotranspiration rate fora watering zone, wherein each processor of the set of one or moreprocessors comprises a portion of an irrigation controller or is inelectronic communication with the irrigation controller; determining adrought category for the watering zone, calculating, using at least oneprocessor of the set of one or more processors, an adjusted landscapeevapotranspiration rate for the watering zone based on the determineddrought category; and adjusting, using at least one processor of the setof one or more processors, the watering schedule for the watering zonein accordance with the adjusted landscape evapotranspiration rate. 9.The method of claim 8, wherein the calculating the adjusted landscapeevapotranspiration rate comprises multiplying a drought factorassociated with the determined drought category by the landscapeevapotranspiration rate.
 10. The method of claim 9, wherein the adjustedlandscape evapotranspiration rate is less than the landscapeevapotranspiration rate.
 11. The method of claim 9, wherein the droughtfactor, within a specified range, is selectable by a user.
 12. Themethod of claim 8, wherein the drought category is determined based onuser input specifying the drought category.
 13. The method of claim 8,wherein the drought category is determined based on drought data and anestimated geographic location of the watering zone.
 14. The method ofclaim 8, wherein the irrigation controller comprises at least two of aserver, a local device, and a mobile end-user device.
 15. A computerprogram product for adjusting a watering schedule stored on anirrigation controller based on determined drought conditions, theirrigation controller being configurable to control irrigation of awatering zone in accordance with the watering schedule, the computerprogram product comprising: a non-transitory computer readable medium;and computer program code, encoded on the non-transitory computerreadable medium, configured to cause at least one processor of a set ofone or more processors to perform steps comprising: formulating awatering schedule for a watering zone based on at least a landscapeevapotranspiration rate for the watering zone; determining a droughtcategory for the watering zone, calculating an adjusted landscapeevapotranspiration rate for the watering zone based on the determineddrought category; and adjusting the watering schedule for the wateringzone in accordance with the adjusted landscape evapotranspiration rate.16. The computer program product of claim 15, wherein the calculatingthe adjusted landscape evapotranspiration rate comprises multiplying adrought factor associated with the determined drought category by thelandscape evapotranspiration rate.
 17. The computer program product ofclaim 15, wherein the adjusted landscape evapotranspiration rate is lessthan the landscape evapotranspiration rate.
 18. The computer programproduct of claim 15, wherein the drought category is determined based onuser input specifying the drought category.
 19. The computer programproduct of claim 15, wherein the drought category is determined based ondrought data and an estimated geographic location of the watering zone.20. The computer program product of claim 15, wherein the irrigationcontroller comprises at least two of a server, a local device, and amobile end-user device.